From: Christoph Lameter <clameter@engr.sgi.com>
To: Andi Kleen <ak@suse.de>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Andrew Morton <akpm@osdl.org>, Benjamin LaHaise <bcrl@kvack.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] use local_t for page statistics
Date: Mon, 9 Jan 2006 12:54:32 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.62.0601091253240.4061@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200601070401.47618.ak@suse.de>
On Sat, 7 Jan 2006, Andi Kleen wrote:
> On Saturday 07 January 2006 03:52, Nick Piggin wrote:
>
> > No. On many load/store architectures there is no good way to do local_t,
> > so something like ppc32 or ia64 just uses all atomic operations for
>
> well, they're just broken and need to be fixed to not do that.
I tried to use local_t on ia64 for page statistics and have to agree with
Nick. local_t has highly arch specific semantics.
--
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>
next prev parent reply other threads:[~2006-01-09 20:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 21:53 Benjamin LaHaise
2006-01-07 0:33 ` Andrew Morton
2006-01-07 1:00 ` Marcelo Tosatti
2006-01-07 2:52 ` Nick Piggin
2006-01-07 3:01 ` Andi Kleen
2006-01-07 3:19 ` Nick Piggin
2006-01-07 3:25 ` Andi Kleen
2006-01-07 3:48 ` Nick Piggin
2006-01-07 4:03 ` Andi Kleen
2006-01-09 20:54 ` Christoph Lameter [this message]
2006-01-07 3:07 ` Andrew Morton
2006-01-09 18:26 ` Benjamin LaHaise
2006-01-09 20:52 ` 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=Pine.LNX.4.62.0601091253240.4061@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bcrl@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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