From: Nigel Cunningham <ncunningham@cyclades.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, Hugh Dickins <hugh@veritas.com>,
Andrea Arcangeli <andrea@suse.de>,
Linux Memory Management List <linux-mm@kvack.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Lockless pagecache perhaps for 2.6.18?
Date: Sun, 26 Mar 2006 20:21:40 +1000 [thread overview]
Message-ID: <200603262021.46276.ncunningham@cyclades.com> (raw)
In-Reply-To: <20060323081100.GE26146@wotan.suse.de>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
Hi Nick.
On Thursday 23 March 2006 18:11, Nick Piggin wrote:
> Hi,
>
> Would there be any objection to having my lockless pagecache patches
> merged into -mm, for a possible mainline merge after 2.6.17 (ie. if/
> when the mm hackers feel comfortable with it).
>
> There are now just 3 patches: 15 files, 312 insertions, 81 deletions
> for the core changes, including RCU radix-tree. (not counting those
> last two I just sent you Andrew (VM_BUG_ON, find_trylock_page))
>
> It is fairly well commented, and not overly complex (IMO) compared
> with other lockless stuff in the tree now.
>
> My main motivation is to get more testing and more serious reviews,
> rather than trying to clear a fast path into mainline.
>
> Nick
Can I get a pointer to the patches and any docs please? Since I save the page
cache separately, I'd need a good understanding of the implications of the
changes.
Regards,
Nigel
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-03-26 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 8:11 Nick Piggin
2006-03-23 8:24 ` Ingo Molnar
2006-03-23 18:07 ` Christoph Lameter
2006-03-23 20:51 ` Hugh Dickins
2006-03-26 10:21 ` Nigel Cunningham [this message]
2006-03-27 0:43 ` Nick Piggin
2006-03-27 0:54 ` Nigel Cunningham
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=200603262021.46276.ncunningham@cyclades.com \
--to=ncunningham@cyclades.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
/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