3 ms·
Then perhaps you might be serve better by the linked article, which is kinda the "dumbed down" version of the Drepper whitepaper. But I don't see why detail is
by ajross 17y ago
Then perhaps you might be serve better by the linked article, which is kinda the "dumbed down" version of the Drepper whitepaper. But I don't see why detail is bad. The Drepper paper is pretty much the only place, short of JEDEC specs and manufacturer datasheets, where you can get an exposition about how modern DRAM works.
(FWIW: his similar whitepapers on ELF shared libraries and glibc TLS are equally great, and also pretty much the canonical review documents on those subjects.)
- palish 17y agoBut I don't see why detail is bad. Too much detail is bad because it hides the relevant knowledge. That is, there are certain paragraphs / certain images that the programmer will remember. Those are the important components. Brevity is good.
- Groxx 17y agoToo much detail is bad in the same way that an intro biology course flooding you with chemical equations for bodily functions (when chem is not a prerequisite), literally hundreds of new terms, many of which are fairly isolated, and a hundred medium-rare diseases is bad. What do you end up remembering? "Body-stuff is hard." And 90% of what you read falls out of your head in a year, along with 90% of the useful stuff. If it's trimmed down, you may lose 50%, and 50% of the useful stuff, which covers all of the generally useful stuff in the massive 10-kilo textbook that covers more than a biochem grad student remembers. Fewer relatively-unrelated (or seen-as-useless) facts also make it easier to form logical connections with the remaining facts, which help you remember and apply what you've learned.