linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: Nick Piggin <npiggin@suse.de>, Andrew Morton <akpm@osdl.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [patch 2/2] mm: lockless pagecache
Date: Mon, 31 Jul 2006 19:34:27 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0607311923020.11821@blonde.wat.veritas.com> (raw)
In-Reply-To: <44CE2365.6040605@shadowen.org>

On Mon, 31 Jul 2006, Andy Whitcroft wrote:
> > Index: linux-2.6/mm/filemap.c
> > ===================================================================
> > --- linux-2.6.orig/mm/filemap.c
> > +++ linux-2.6/mm/filemap.c
> > @@ -613,11 +613,22 @@ struct page *find_trylock_page(struct ad
> ....
> 
> This one has me puzzled.  This seem to no longer lock the page at all when
> returning it.  It seems the semantics of this has changed wildly. Also
> find_lock_page below still seems to lock the page, the semantic seems
> maintained there?  I think I am expecting to find a TestSetPageLocked()
> in the new version too?

Whereas find_get_page, which should be the centre-piece of the patch,
is unchanged and using read_lock_irq(&mapping->tree_lock) as before.

It looks like the code seen in find_trylock_page is actually what should
be in find_get_page.  It doesn't matter too much what find_trylock_page
does, since it's deprecated and nothing in tree now uses it; but it ought
to TestSetPageLocked and page_cache_release somewhere, to suit remaining
out-of-tree users.

Hugh

--
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:[~2006-07-31 18:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26  6:39 Nick Piggin
2006-07-31 15:36 ` Andy Whitcroft
2006-07-31 18:34   ` Hugh Dickins [this message]
2006-08-01  9:04   ` 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=Pine.LNX.4.64.0607311923020.11821@blonde.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=linux-mm@kvack.org \
    --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