What Every Programmer Should Know About Memory
people.freebsd.org · 92,193 words · saved by 7 readers
N/A
# link_19jkogybix4.pdf ## Metadata - PDFFormatVersion=1.5 - IsLinearized=false - IsAcroFormPresent=false - IsXFAPresent=false - IsCollectionPresent=false - IsSignaturesPresent=false - CreationDate=D:20060619205600-08'00' - Author=Ulrich Drepper Red Hat, Inc. drepper@redhat.com - Title=What Every Programmer Should Know About Memory - Creator=LaTeX with hyperref package - Producer=pdfTeX-1.40.3 - Keywords=Linux, Programming, Memory, Cache, Performance, Hardware - ModDate=D:20071121175207-08'00' - Trapped=False - Custom.PTEX.Fullbanner=This is pdfTeX, Version 3.141592-1.40.3-2.2 (Web2C 7.5.6) kpa
saved by
- Kevin Wang
- Varun Shenoy
- Julian Quevedo
- Ayodeji Adesegun
- Benedict Neo
- Gabriel Bartmanovicz
- David Jihoon Kim
related reading
- What Every Programmer Should Know About Memoryakkadia.org
- What every programmer should know about memory, Part 1 [LWN.net]lwn.net
- A very concrete explanation of how a cache worksparksb.github.io
- Intro - Putting the "You" in CPUcpu.land
- research!rsc: Hardware Memory Models (Memory Models, Part 1)research.swtch.com
- CSAPP_2016.pdfcs.sfu.ca
- The "Basics" | Putting the "You" in CPUcpu.land
- Memory location matters for performancepythonspeed.com
- Your RAM Has a 60 Year Old Design Flaw. I Bypassed It.youtube.com
- Linux kernel memory barriers — The Linux Kernel documentationdocs.kernel.org
- Modern Microprocessors - A 90-Minute Guide!lighterra.com
- Building a better memory systemmichaelnotebook.com