All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Linux Memory Management <linux-mm@kvack.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.13] lockless pagecache 2/7
Date: Sat, 03 Sep 2005 07:26:45 +1000	[thread overview]
Message-ID: <4318C395.1080203@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.62.0509021123290.15836@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Fri, 2 Sep 2005, Nick Piggin wrote:
> 
> 
>>Implement atomic_cmpxchg for i386 and ppc64. Is there any
>>architecture that won't be able to implement such an operation?
> 
> 
> Something like that used to be part of the page fault scalability 
> patchset. You contributed to it last year. Here is the latest version of 
> that. May need some work though.
> 

Thanks Christoph, I think this will be required to support 386.
In the worst case, we could provide a fallback path and take
->tree_lock in pagecache lookups if there is no atomic_cmpxchg,
however I would much prefer all architectures get an atomic_cmpxchg,
and I think it should turn out to be a generally useful primitive.

I may trim this down to only provide what is needed for atomic_cmpxchg
if that is OK?

Nick

-- 
SUSE Labs, Novell Inc.

Send instant messages to your online friends http://au.messenger.yahoo.com 

WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Linux Memory Management <linux-mm@kvack.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.13] lockless pagecache 2/7
Date: Sat, 03 Sep 2005 07:26:45 +1000	[thread overview]
Message-ID: <4318C395.1080203@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.62.0509021123290.15836@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Fri, 2 Sep 2005, Nick Piggin wrote:
> 
> 
>>Implement atomic_cmpxchg for i386 and ppc64. Is there any
>>architecture that won't be able to implement such an operation?
> 
> 
> Something like that used to be part of the page fault scalability 
> patchset. You contributed to it last year. Here is the latest version of 
> that. May need some work though.
> 

Thanks Christoph, I think this will be required to support 386.
In the worst case, we could provide a fallback path and take
->tree_lock in pagecache lookups if there is no atomic_cmpxchg,
however I would much prefer all architectures get an atomic_cmpxchg,
and I think it should turn out to be a generally useful primitive.

I may trim this down to only provide what is needed for atomic_cmpxchg
if that is OK?

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-09-02 21:26 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-02  6:25 New lockless pagecache Nick Piggin
2005-09-02  6:25 ` Nick Piggin
2005-09-02  6:28 ` [PATCH 2.6.13] lockless pagecache 1/7 Nick Piggin
2005-09-02  6:29   ` [PATCH 2.6.13] lockless pagecache 2/7 Nick Piggin
2005-09-02  6:30     ` [PATCH 2.6.13] lockless pagecache 3/7 Nick Piggin
2005-09-02  6:30       ` [PATCH 2.6.13] lockless pagecache 4/7 Nick Piggin
2005-09-02  6:31         ` [PATCH 2.6.13] lockless pagecache 5/7 Nick Piggin
2005-09-02  6:32           ` [PATCH 2.6.13] lockless pagecache 6/7 Nick Piggin
2005-09-02  6:32             ` [PATCH 2.6.13] lockless pagecache 7/7 Nick Piggin
2005-09-09 13:00               ` Christoph Lameter
2005-09-09 13:00                 ` Christoph Lameter
2005-09-09 15:23                 ` Nick Piggin
2005-09-09 15:23                   ` Nick Piggin
2005-09-09  5:36           ` [PATCH 2.6.13] lockless pagecache 5/7 Christoph Lameter
2005-09-09  5:36             ` Christoph Lameter
2005-09-09  6:22             ` Nick Piggin
2005-09-09  6:22               ` Nick Piggin
2005-09-02 13:08     ` [PATCH 2.6.13] lockless pagecache 2/7 Alan Cox
2005-09-02 13:08       ` Alan Cox
2005-09-02 20:41       ` Andi Kleen
2005-09-02 20:41         ` Andi Kleen
2005-09-02 21:12         ` David S. Miller
2005-09-02 21:12           ` David S. Miller, Andi Kleen
2005-09-02 21:43           ` Nick Piggin
2005-09-02 21:43             ` Nick Piggin
2005-09-02 21:22         ` Nick Piggin
2005-09-02 21:22           ` Nick Piggin
2005-09-02 21:31           ` David S. Miller
2005-09-02 21:31             ` David S. Miller, Nick Piggin
2005-09-02 21:47             ` Nick Piggin
2005-09-02 21:47               ` Nick Piggin
2005-09-02 21:57               ` David S. Miller
2005-09-02 21:57                 ` David S. Miller, Nick Piggin
2005-09-02 23:57           ` Alan Cox
2005-09-02 23:57             ` Alan Cox
2005-09-03  1:40             ` Nick Piggin
2005-09-03  1:40               ` Nick Piggin
2005-09-03 17:31               ` Alan Cox
2005-09-03 17:31                 ` Alan Cox
2005-09-04  1:01                 ` Nick Piggin
2005-09-04  1:01                   ` Nick Piggin
2005-09-04  8:20                   ` Alan Cox
2005-09-04  8:20                     ` Alan Cox
2005-09-06  1:03                     ` Nick Piggin
2005-09-06  1:03                       ` Nick Piggin
2005-09-02 18:26     ` Christoph Lameter
2005-09-02 18:26       ` Christoph Lameter
2005-09-02 21:26       ` Nick Piggin [this message]
2005-09-02 21:26         ` Nick Piggin
2005-09-03  1:33         ` Christoph Lameter
2005-09-03  1:33           ` Christoph Lameter
2005-09-02  6:45 ` New lockless pagecache Nick Piggin
2005-09-02  6:45   ` Nick Piggin
2005-09-15 19:50   ` Alok kataria
2005-09-16  3:12     ` Nick Piggin
2005-09-16  3:12       ` Nick Piggin

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=4318C395.1080203@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=clameter@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.