From: Nigel Cunningham <ncunningham@cyclades.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Nick Piggin <npiggin@suse.de>, 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: Mon, 27 Mar 2006 10:54:16 +1000 [thread overview]
Message-ID: <200603271054.22272.ncunningham@cyclades.com> (raw)
In-Reply-To: <4427353A.6060905@yahoo.com.au>
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
Hi Nick.
On Monday 27 March 2006 10:43, Nick Piggin wrote:
> Nigel Cunningham wrote:
> > 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.
>
> Hi Nigel,
>
> http://www.kernel.org/pub/linux/kernel/people/npiggin/patches/lockless/2.6.
>16-rc5/
>
> There are some patches... a lot of them, but only the last 5 in the series
> matter (the rest are pretty much in 2.6.16-head).
>
> There is also a small doc on the lockless radix-tree in that directory. I'm
> in the process of writing some documentation on the lockless pagecache
> itself...
>
> You probably don't need to worry too much unless you are testing
> page_count() under the tree_lock, held for writing, expecting that to
> stabilise page_count. In which case I could have a look at your code and
> see if it would be a problem.
Thanks.
I'm not far from head now, so guess I have no problems with the rest.
From what you say about the other patches, I think I'm fine as far as the rest
go too. I was mostly concerned that the modifications might make it possible
for the lru to start changing while the image is being written. It looks to
me now like I was being too paranoid (which isn't necessarily a bad thing, is
it?).
Regards,
Nigel
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-03-27 0:54 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
2006-03-27 0:43 ` Nick Piggin
2006-03-27 0:54 ` Nigel Cunningham [this message]
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=200603271054.22272.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=nickpiggin@yahoo.com.au \
--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