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 7/7
Date: Sat, 10 Sep 2005 01:23:26 +1000 [thread overview]
Message-ID: <4321A8EE.9080206@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.62.0509090549110.7332@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> For Itanium (and I guess also for ppc64 and sparch64) the performance of
> write_lock/unlock is the same as spin_lock/unlock. There is at least
> one case where concurrent reads would be allowed without this patch.
>
Yep, I picked up another one that was easy to make lockless (I'll send
out a new patchset soon), however the tagged lookup that was under read
lock is changed to a spin lock.
It shouldn't be too difficult to make the tag lookups (find_get_pages_tag)
lockless, however I just haven't gotten around to looking at the write
side of the tagging yet.
When that is done, there should be no more read locks at all.
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>
next prev parent reply other threads:[~2005-09-09 15:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 6:25 New lockless pagecache 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 15:23 ` Nick Piggin [this message]
2005-09-09 5:36 ` [PATCH 2.6.13] lockless pagecache 5/7 Christoph Lameter
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 20:41 ` Andi Kleen
2005-09-02 21:12 ` David S. Miller, Andi Kleen
2005-09-02 21:43 ` Nick Piggin
2005-09-02 21:22 ` Nick Piggin
2005-09-02 21:31 ` David S. Miller, Nick Piggin
2005-09-02 21:47 ` Nick Piggin
2005-09-02 21:57 ` David S. Miller, Nick Piggin
2005-09-02 23:57 ` Alan Cox
2005-09-03 1:40 ` Nick Piggin
2005-09-03 17:31 ` Alan Cox
2005-09-04 1:01 ` Nick Piggin
2005-09-04 8:20 ` Alan Cox
2005-09-06 1:03 ` Nick Piggin
2005-09-02 18:26 ` Christoph Lameter
2005-09-02 21:26 ` Nick Piggin
2005-09-03 1:33 ` Christoph Lameter
2005-09-02 6:45 ` New lockless pagecache Nick Piggin
2005-09-15 19:50 ` Alok kataria
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=4321A8EE.9080206@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox