Posted Aug 31, 2006 22:32 UTC (Thu) by giraffedata
Parent article: Resource beancounters
There are some concerns about how accounting for shared resources is handled - does the process group which first faults in the C library get charged for the whole thing, giving others a free ride?
The few times I've tried to resolve the kernel memory accounting problem, I've had to quit because most of the resource is shared.
Also, kernel code usually can't tolerate having no memory available to it. The only reason the kernel works at all today is that things are done to make it unlikely that there isn't a single page of memory available; but with local limits like this, it would happen a lot.
to post comments)