Christoph Lameter wrote:
On Thu, 8 Dec 2005, Nick Piggin wrote:
Christoph Lameter wrote:
On Wed, 7 Dec 2005, Nick Piggin wrote:
Sorry, I think I meant: why don't you just use the "add all counters
from all per-cpu of the node" in order to find the node-statistic?
which function is that?
I'm thinking of get_page_state_node... but that's not quite the same
thing. I guess sum all per-CPU counters from all zones in the node,
but that's going to be costly on big machines.
The per cpu counters count when a cpu did an allocation. They do not count
on which node the allocation was done and are thereofre not useful to
determine the memory use on one node.
Yes, not that exact function of course.
So I'm not sure, I guess I don't have any bright ideas... there is the
batching approach used by current pagecache_acct - is something like
that not sufficient either?
The framework provides a similar approach by keeping differential
counters for each processor.
But the accounting delay has the unbounded error problem that the
batching approach does not.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
