.net pdf 417

.net pdf 417

.net pdf 417

.net pdf 417

.net pdf 417

.net pdf 417,

.net pdf 417,

.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,

.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,

.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,
.net pdf 417,

Cold misses are fundamental and are determined by the working set of the program in question, rather than by the cache organization However, varying the block size directly affects the number of cold misses experienced by a cache Intuitively, this becomes obvious by considering two extreme block sizes: a cache with a block size of one word will experience a cold miss for every unique word referenced by the program (this forms the upper bound for the number of cold misses in any cache organization), while a cache with an infinite block size will experience only a single cold miss The latter is true because the very first reference will install all addressable memory into the cache, resulting in no additional misses of any type Of course, practical cache organizations have a finite block size somewhere between these two endpoints, usually in the range of 16 to 512 bytes Capacity misses are not fundamental but are determined by the block size and capacity of the cache Clearly, as capacity increases, the-number of capacity misses is reduced, since a larger cache is able to capture a larger share of the program's working set In contrast, as block size increases, the number of unique blocks that can reside simultaneously in a cache of fixed capacity decreases Larger blocks tend to be utilized more poorly, since the probability that the program will access all the words in a particular block decreases as the block gets bigger, leading to a lower effective capacity As a result, with fewer unique blocks and a decreased probability that all words in each block are useful, a larger block size usually results in an increased number of capacity misses However, programs that efficiently utilize all the contents of large blocks would not experience such an increase Conflict misses are also not fundamental and are determined by the block size, the capacity, and the associativity of the cache Increased capacity invariably reduces the number of conflict misses, since the probability of a conflict between two accessed blocks is reduced as the total number of blocks that can reside in the cache simultaneously increases As with capacity misses, a larger number of smaller blocks reduces the probability of a conflict and improves the effective capacity, resulting in likely fewer conflict misses Similariy, increased associativity will almost invariably reduce the number of conflict misses (Problem 25 in the homework will ask you to construct a counterexample to this case).

You may have noticed the tabs, spaces, and blank lines scattered throughout the sample programs. These are known in C as white space. With a few exceptions, white space is ignored by C compilers. Believe it or not, as far as the C compiler goes, this program:

#include <stdio.h> int main (int argc, const char * argv[]) { int myInt;myInt = 5 ; printf("myInt=",myInt);}

In this lab, you ll compare the features of impact, inkjet, and laser printers using the Internet At the end of this lab, you ll be able to Recognize the key differences between impact, inkjet, and laser printers Identify and visit Web sites on the Internet dedicated to printers and printer troubleshooting

is equivalent to this program:

int main (int argc, const char * argv[]) { int myInt; myInt = 5; printf( "myInt =", myInt ); }

The materials you need for this lab are A working computer with Windows A connection to the Internet Access to either an inkjet printer or a laser printer

The C compiler doesn t care if you put five statements per line or if you put 20 carriage returns between your statements and your semicolons. One thing the compiler won t let you do is place white space in the middle of a word, such as a variable or function name. For example, this line of code won t compile:

.

my Int = 5;

Instead of a single variable named myInt, the compiler sees two items, one named my and the other named Int. Too much white space can confuse the compiler. Too little white space can also confuse the compiler. For example, this line of code won t compile:

A trip to your local computer store or other retailer with a good selection of printers would be bene cial for a general knowledge of printers

intmyInt;

The compiler needs at least one piece of white space to tell it where the type ends and where the variable begins. On the other hand, as you ve already seen, this line compiles just fine: