From: Andi Kleen <ak@suse.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org, pj@sgi.com, akpm@osdl.org
Subject: Re: [RFC] Use ZVCs for numa statistics.
Date: Wed, 14 Jun 2006 07:48:32 +0200 [thread overview]
Message-ID: <200606140748.32032.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0606131808180.1225@schroedinger.engr.sgi.com>
On Wednesday 14 June 2006 03:13, Christoph Lameter wrote:
> The numa statistics are really event counters. But they are per
> node and therefore we can use the per zone feature to easily
> implement what we need.
>
> Remove the special statistics for numa and replace them with
> zoned vm counters.
Looks reasonable.
>
> This has the side effect that global sums of these events now show up
> in /proc/vmstat.
>
> I am not sure if this is a good approach. It certainly removes a
> lot of code and may place the counters more securely into the
> pcp cacheline but the implementation may be less efficient than the
> original code (not tested yet) since the ZVC require the disabling
> of interrupts.
I still hope that can be avoided by using local_t properly.
-Andi
prev parent reply other threads:[~2006-06-14 5:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 1:13 [RFC] Use ZVCs for numa statistics Christoph Lameter
2006-06-14 5:48 ` Andi Kleen [this message]
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=200606140748.32032.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.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