Linked by Thom Holwerda on Thu 4th Oct 2007 15:23 UTC, submitted by diegocg
General Development "Ulrich Drepper [the gnu libc project leader] recently approached us [LWN] asking if we would be interested in publishing a lengthy document he had written on how memory and software interact. Memory usage is often the determining factor in how software performs, but good information on how to avoid memory bottlenecks is hard to find. This article is the first in a serie of articles (the original has over 100 pages) that will get published on LWN weekly. Once the entire series is out, Ulrich will be releasing the full text."
Thread beginning with comment 276132
To read all comments associated with this story, please click here.
hmmmm....
by BluenoseJake on Thu 4th Oct 2007 16:01 UTC
BluenoseJake
Member since:
2005-08-11

Title should read "What Every GNU/Linux Programmer Should Know About Memory, Part 1"

RE: hmmmm....
by ashigabou on Thu 4th Oct 2007 16:32 in reply to "hmmmm...."
ashigabou Member since:
2005-11-11

Not really. Even if the author says he is only interested in linux, the first part is mostly concerned with hardware principles, which are general enough to be useful for other people.

Reply Parent Bookmark Score: 8

RE: hmmmm....
by Vanders on Thu 4th Oct 2007 18:37 in reply to "hmmmm...."
Vanders Member since:
2005-07-06

If we're going to try to be pedantic, that should read "What Every Glibc-using Programmer Should Know About Memory, Part 1". Glibc runs on at least four different kernels, at my last count.

Reply Parent Bookmark Score: 1

RE[2]: hmmmm....
by dasher on Thu 4th Oct 2007 18:54 in reply to "RE: hmmmm...."
dasher Member since:
2007-10-04

I'v read the first 2 installments. And they are both quite generic. Nothing at all glibc specific, or even close. As someone who uses glibc, I'm anxiously *waiting* for the more specific segments!

Reply Parent Bookmark Score: 1