Transcription of What Every Programmer Should Know About Memory
{{id}} {{{paragraph}}}
Example: biology
What Every Programmer Should Know About Memory
What Every Programmer Should Know About MemoryUlrich DrepperRed Hat, 21, 2007 AbstractAs CPU cores become both faster and more numerous, the limiting factor for most programs isnow, and will be for some time, Memory access. Hardware designers have come up with evermore sophisticated Memory handling and acceleration techniques such as CPU caches butthese cannot work optimally without some help from the Programmer . Unfortunately, neitherthe structure nor the cost of using the Memory subsystem of a computer or the caches on CPUsis well understood by most programmers. This paper explains the structure of Memory subsys-tems in use on modern commodity hardware, illustrating why CPU caches were developed, howthey work, and what programs Should do to achieve optimal performance by utilizing IntroductionIn the early days computers were much simpler.
sential for an understanding of the rest of the document. Section 4 describes briefly how virtual memory is imple-mented. This is also required groundwork for the rest. Section 5 goes into a lot of detail about Non Uniform Memory Access (NUMA) systems. Section 6 is the central section of this paper. It brings to-
Loading..
Tags:
Information
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document: