linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andi Kleen <ak@suse.de>
Cc: Christoph Lameter <clameter@sgi.com>,
	linux-kernel@vger.kernel.org, Hugh Dickins <hugh@veritas.com>,
	linux-mm@kvack.org,
	Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: [RFC 1/6] Framework
Date: Mon, 12 Dec 2005 15:14:53 +1100	[thread overview]
Message-ID: <439CF93D.5090207@yahoo.com.au> (raw)
In-Reply-To: <20051212035631.GX11190@wotan.suse.de>

Andi Kleen wrote:
> On Mon, Dec 12, 2005 at 02:46:42PM +1100, Nick Piggin wrote:
> 
>>Christoph Lameter wrote:
>>
>>
>>>+/*
>>>+ * For use when we know that interrupts are disabled.
>>>+ */
>>>+static inline void __mod_zone_page_state(struct zone *zone, enum 
>>>zone_stat_item item, int delta)
>>>+{
>>
>>Before this goes through, I have a full patch to do similar for the
>>rest of the statistics, and which will make names consistent with what
>>you have (shouldn't be a lot of clashes though).
> 
> 
> I also have a patch to change them all to local_t, greatly simplifying
> it (e.g. the counters can be done inline then) 
> 

Cool. That is a patch that should go on top of mine, because most of
my patch is aimed at moving modifications under interrupts-off sections,
so you would then be able to use __local_xxx operations very easily for
most of the counters here.

However I'm still worried about the use of locals tripling the cacheline
size of a hot-path structure on some 64-bit architectures. Probably we
should get them to try to move to the atomic64 scheme before using
local_t here.

Nick

-- 
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-12  4:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-10  0:54 [RFC 0/6] Zoned VM stats Christoph Lameter
2005-12-10  0:54 ` [RFC 1/6] Framework Christoph Lameter
2005-12-10  3:32   ` Andi Kleen
2005-12-12 16:32     ` Christoph Lameter
2005-12-12  3:46   ` Nick Piggin
2005-12-12  3:56     ` Andi Kleen
2005-12-12  4:14       ` Nick Piggin [this message]
2005-12-12  4:21         ` Andi Kleen
2005-12-12  4:28           ` Nick Piggin
2005-12-12  4:51             ` Andi Kleen
2005-12-12  7:05               ` Nick Piggin
2005-12-10  0:54 ` [RFC 2/6] Make nr_mapped a per zone counter Christoph Lameter
2005-12-10  0:54 ` [RFC 3/6] Make nr_pagecache " Christoph Lameter
2005-12-11 18:32   ` Marcelo Tosatti
2005-12-11 19:48     ` Andi Kleen
2005-12-11 20:49       ` Marcelo Tosatti
2005-12-12  3:51         ` Nick Piggin
2005-12-12 11:57           ` Marcelo Tosatti
2005-12-12 16:34             ` Christoph Lameter
2005-12-10  0:55 ` [RFC 4/6] Expanded node and zone statistics Christoph Lameter
2005-12-10  0:55 ` [RFC 5/6] Make nr_slab a per zone counter Christoph Lameter
2005-12-10  0:55 ` [RFC 6/6] Make nr_pagecache " 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=439CF93D.5090207@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=ak@suse.de \
    --cc=clameter@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