From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Hugh Dickins <hugh@veritas.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [patch 0/6] lockless pagecache
Date: Sat, 17 Nov 2007 10:48:11 +0100 [thread overview]
Message-ID: <1195292891.6739.1.camel@twins> (raw)
In-Reply-To: <20071111084556.GC19816@wotan.suse.de>
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
On Sun, 2007-11-11 at 09:45 +0100, Nick Piggin wrote:
> Hi,
>
> I wonder what everyone thinks about getting the lockless pagecache patch
> into -mm? This version uses Hugh's suggestion to avoid a smp_rmb and a load
> and branch in the lockless lookup side, and avoids some atomic ops in the
> reclaim path, and avoids using a page flag! The coolest thing about it is
> that it speeds up single-threaded pagecache lookups...
>
> Patches are against latest git for RFC.
Full set
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-17 9:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 8:45 [patch 0/6] lockless pagecache Nick Piggin
2007-11-11 8:47 ` [patch 1/6] mm: readahead scan lockless Nick Piggin
2007-11-11 8:49 ` [patch 2/6] radix-tree: gang_lookup_slot Nick Piggin
2007-11-11 8:50 ` [patch 3/6] mm: speculative get page Nick Piggin
2007-11-12 20:21 ` Christoph Lameter
2007-11-13 0:35 ` Nick Piggin
2007-11-13 0:37 ` Christoph Lameter
2007-11-13 0:51 ` Nick Piggin
2007-11-11 8:51 ` [patch 4/6] mm: lockless pagecache lookups Nick Piggin
2007-11-11 8:51 ` [patch 5/6] mm: spinlock tree_lock Nick Piggin
2007-11-11 8:52 ` [patch 6/6] mm: speculative refcount debug Nick Piggin
2007-11-17 9:48 ` Peter Zijlstra [this message]
2007-11-17 20:16 ` [patch 0/6] lockless pagecache Hugh Dickins
2007-11-19 22:58 ` Nick Piggin
2008-01-09 15:45 ` Peter Zijlstra
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=1195292891.6739.1.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.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.