linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: linux-kernel@vger.kernel.org, Hugh Dickins <hugh@veritas.com>,
	linux-mm@kvack.org, Andi Kleen <ak@suse.de>,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: [RFC 1/3] Framework for accurate node based statistics
Date: Thu, 08 Dec 2005 11:13:06 +1100	[thread overview]
Message-ID: <43977A92.3090206@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.62.0512071559170.26144@schroedinger.engr.sgi.com>

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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2005-12-08  0:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-06 18:28 Christoph Lameter
2005-12-06 18:28 ` [RFC 2/3] Make nr_mapped a per node counter Christoph Lameter
2005-12-06 23:05   ` Nick Piggin
2005-12-06 18:28 ` [RFC 3/3] Make nr_pagecache " Christoph Lameter
2005-12-06 18:35 ` [RFC 1/3] Framework for accurate node based statistics Andi Kleen
2005-12-06 19:08   ` Christoph Lameter
2005-12-06 19:26     ` Andi Kleen
2005-12-06 19:36       ` Christoph Lameter
2005-12-06 20:06         ` Andi Kleen
2005-12-06 22:52           ` Christoph Lameter
2005-12-07  5:50             ` Keith Owens
2005-12-07 18:24               ` Christoph Lameter
2005-12-06 23:08 ` Nick Piggin
2005-12-06 23:37   ` Christoph Lameter
2005-12-06 23:40     ` Christoph Lameter
2005-12-07  6:44     ` Nick Piggin
2005-12-07 18:27       ` Christoph Lameter
2005-12-07 22:59         ` Nick Piggin
2005-12-08  0:02           ` Christoph Lameter
2005-12-08  0:13             ` Nick Piggin [this message]
2005-12-08  0:35               ` Christoph Lameter
2005-12-07 18:39 Luck, Tony
2005-12-07 18:47 ` Christoph Lameter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43977A92.3090206@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=ak@suse.de \
    --cc=clameter@engr.sgi.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marcelo.tosatti@cyclades.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox