| charles hottel 2005-07-24, 10:01 pm |
| The "old" locality of reference idea was to keep your code and data close
together (on the same page) to reduce paging. On IBM mainframe systems (and
perhaps on others also) that have instruction pipelines/caches, this "old"
method can actually cause a performance hit. This is caused when there is
data in the cache that is changed causing the cache contents be invalidated
and causing a disruption of the instruction pipeline.. The "new" locality
of reference idea is to keep your data at separate from your instructions by
at least the size of the cache. One way to do this is to make your programs
reentrant.
There is a discussion of the at:
http://groups-beta.google.com/group...fbc55e?q=cache&
Top post - no more below.
"Pete Dashwood" <dashwood@enternet.co.nz> wrote in message
news:3k86utFl4gssU1@individual.net...
>
> "Clark Morris" <cfmtech@istar.ca> wrote in message
> news:e1atd11fi2cshuqsgg11l78qp1n840102p@
4ax.com...
<snip>
[color=darkred]
>
> In modern systems 'locality of reference' is almost irrelevant, especially
> when multitasking is proceeding anyway.
|