15 213 Introduction to Computer Systems Khaled A Harras August 24 2009 Topics Theme Five great realities of computer systems How this fits within CS curriculum class01a ppt Slide Credits Prof Randal E Bryant 15 213 F 09 Course Theme Abstraction is good but don t forget reality Courses to date emphasize abstraction Abstract data types Asymptotic analysis These abstractions have limits Especially in the presence of bugs Need to understand underlying implementations Useful outcomes Become more effective programmers z Able to find and eliminate bugs efficiently z Able to tune program performance Prepare for later systems classes in CS ECE z Compilers Operating Systems Networks Computer Architecture Embedded Systems 2 15 213 Intro to Computer Systems Fall 2009 Great Reality 1 Int s are not Integers Float s are not Reals Examples Is x2 0 z Float s Yes z Int s 40000 40000 1600000000 50000 50000 Is x y z x y z z Unsigned Signed Int s Yes z Float s 1e20 1e20 3 14 3 14 1e20 1e20 3 14 3 15 213 Intro to Computer Systems Fall 2009 Computer Arithmetic Does not generate random values Arithmetic operations have important mathematical properties Cannot assume usual properties Due to finiteness of representations Integer operations satisfy ring properties z Commutativity associativity distributivity Floating point operations satisfy ordering properties z Monotonicity values of signs Observation 4 Need to understand which abstractions apply in which contexts Important issues for compiler writers and serious application programmers 15 213 Intro to Computer Systems Fall 2009 Great Reality 2 You ve got to know assembly Chances are you ll never write program in assembly Compilers are much better more patient than you are Understanding assembly key to machine level execution model Behavior of programs in presence of bugs z High level language model breaks down Tuning program performance z Understanding sources of program inefficiency Implementing system software z Compiler has machine code as target z Operating systems must manage process state 5 Creating fighting malware z x86 assembly is the language of choice 15 213 Intro to Computer Systems Fall 2009 Assembly Code Example Time Stamp Counter Special 64 bit register in Intel compatible machines Incremented every clock cycle Read with rdtsc instruction Application Measure time required by procedure z In units of clock cycles double t start counter P t get counter printf P required f clock cycles n t 6 15 213 Intro to Computer Systems Fall 2009 Great Reality 3 Memory Matters Random Access Memory is an un physical abstraction Memory is not unbounded It must be allocated and managed Many applications are memory dominated Memory referencing bugs especially pernicious Effects are distant in both time and space Memory performance is not uniform 7 Cache and virtual memory effects can greatly affect program performance Adapting program to characteristics of memory system can lead to major speed improvements 15 213 Intro to Computer Systems Fall 2009 Memory Referencing Bug Example double double fun int fun int i i volatile volatile double double d 1 d 1 3 14 3 14 volatile volatile long long int int a 2 a 2 a i a i 1073741824 1073741824 Possibly Possibly out out of of bounds bounds return d 0 return d 0 fun 0 fun 0 fun 1 fun 1 fun 2 fun 2 fun 3 fun 3 fun 4 fun 4 8 3 14 3 14 3 14 3 14 3 1399998664856 3 1399998664856 2 00000061035156 2 00000061035156 3 14 3 14 then thensegmentation segmentationfault fault 15 213 Intro to Computer Systems Fall 2009 Referencing Bug Explanation 9 Saved State 4 d7 d4 3 d3 d0 2 a 1 1 a 0 0 Location accessed by fun i C does not implement bounds checking Out of range write can affect other parts of program state 15 213 Intro to Computer Systems Fall 2009 Memory Referencing Errors C and C do not provide any memory protection Out of bounds array references Invalid pointer values Abuses of malloc free Can lead to nasty bugs Whether or not bug has any effect depends on system and compiler Action at a distance z Corrupted object logically unrelated to one being accessed z Effect of bug may be first observed long after it is generated How can I deal with this 10 Program in Java Lisp or ML Understand what possible interactions may occur Use or develop tools to detect referencing errors 15 213 Intro to Computer Systems Fall 2009 Memory System Performance Example void copyij int int int i j for i 0 i for j 0 dst i j src 2048 2048 dst 2048 2048 2048 i j 2048 j src i j 59 393 288 clock cycles void copyji int int int i j for j 0 j for i 0 dst i j src 2048 2048 dst 2048 2048 2048 j i 2048 i src i j 1 277 877 876 clock cycles 21 5 times slower Hierarchical memory organization Performance depends on access patterns Measured on 2GHz Intel Pentium 4 z Including how step through multi dimensional array 11 15 213 Intro to Computer Systems Fall 2009 The Memory Mountain Pentium III Xeon 550 MHz 16 KB on chip L1 d cache 16 KB on chip L1 i cache 512 KB off chip unified L2 cache 1200 Read throughput MB s copyij 1000 L1 800 copyji 600 400 xe L2 200 12 15 213 Intro to Computer Systems Fall 2009 2k 8k 32k 128k 512k 2m 8m s15 s13 s11 s9 Stride words Mem s7 s5 s3 s1 0 Working set size bytes Memory Performance Example Implementations of Matrix Multiplication Multiple ways to nest loops ijk ijk for for i 0 i 0 i n i n i i for for j 0 j 0 j n j n j j sum sum 0 0 0 0 for for k 0 k 0 k n k n k k sum sum a i k a i k b k j b k j c i j c i j sum sum 13 jik jik for for j 0 j 0 j n j n j j for for i 0 i 0 i n i n i i sum sum 0 0 0 0 for for k 0 k 0 k n k n k k sum sum a i k a i k b k j b k j c i j c i j sum sum 15 213 Intro to Computer Systems Fall 2009 Matmult Performance Alpha 21164 Too big for L1 Cache Too big for L2 Cache 160 140 120 ijk 100 ikj jik 80 jki kij 60 kji 40 20 0 matrix size n 14 15 213 Intro to Computer Systems Fall 2009 Blocked matmult perf Alpha 21164 160 140 120 100 bijk bikj 80 ijk ikj 60 40 20 0 50 75 100 125 150 175 200 225 250 275 300 325 350 375 400 425 450 475 500 matrix size n 15 15 213 Intro to Computer Systems Fall 2009 Great Reality 4 There s more to performance than asymptotic complexity Constant factors matter too Easily see 10 1 performance range depending on how code written …
View Full Document
Unlocking...