Give as many reasons as you can why locality is a reasonable phenomenon. Give as many examples as you can of situations in which locality simply does not apply.
What will be an ideal response?
This issue will form a major part of the discussion in Chapter 11, Virtual Memory
Management. Locality is simply a reasonable phenomenon. When a program executes an
instruction, there is a high probability that it will execute the next instruction and in fact the
next several instructions.When a data value is read, there is a high probability that nearby
values will be referenced because of array traversals and because programmers tend to put
related variables together.Yet there are situations in which locality does not apply. Information
retrieval programs geared to servicing random requests would not tend to exhibit strong
locality.
You might also like to view...
Assume that your program opens a file stream, has a file connected, and writes to the file. What changes need to be made to make your program write to the screen? (There will be stuff you need to delete and stuff that you need to change.)
What will be an ideal response?
Is this the best way to put the array into descending order?
An array is sorted into ascending order. The following sequence of steps will put the array into descending order: 1) Copy the array into a maxheap 2) Remove the elements from the maxheap and put them in order into the array.
Which two components would be found in a home server computer? (Select two.)
A) Minimum RAM B) Multiple hard drives in a RAID array configuration C) Multiple KVM switches D) Multiple processors E) Dual monitors
The Field dialog box, found on the Quick Parts button, can be used to place fields in a footer.
a. true b. false