linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Hugh Dickins <hugh@veritas.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	npiggin@suse.de, akpm@linux-foundation.org, mpatocka@redhat.com,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [patch 2/8] mm: write_cache_pages AOP_WRITEPAGE_ACTIVATE fix
Date: Sat, 11 Oct 2008 15:05:55 +1100	[thread overview]
Message-ID: <200810111505.55812.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0810101919530.17254@blonde.site>

On Saturday 11 October 2008 05:29, Hugh Dickins wrote:
> On Fri, 10 Oct 2008, Miklos Szeredi wrote:
> > On Fri, 10 Oct 2008, npiggin@suse.de wrote:
> > > In write_cache_pages, if AOP_WRITEPAGE_ACTIVATE is returned, the
> > > filesystem is calling on us to drop the page lock and retry,
> >
> > Are you sure?  It's not what fs.h says.  I think this return value is
> > related to reclaim (and only used by shmfs), and retrying is not the
> > right thing in that case.

Oh, you're absolutely right about that. Sorry, I confused it with
another AOP flag :( Thanks...


> Only used by shmfs nowadays, yes; it means go away for now,
> don't keep on spamming me with this, but try it again later on.
>
> Though I didn't invent it, it's very much my fault that it
> still exists: I've had a patch to remove it (setting PageActive
> instead, ending that horrid "but in this case, return with the
> page still locked") for about a year, but still hadn't got around
> to verifying that it really does what's intended, before the more
> interesting split-lru changes reached -mm, and I thought it polite
> to hold off for now (though in fact there's almost no conflict).
> I'll get there...

No big deal.

  reply	other threads:[~2008-10-11  4:06 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 15:50 [patch 0/8] write_cache_pages fixes npiggin
2008-10-09 15:50 ` [patch 1/8] mm: write_cache_pages cyclic fix npiggin
2008-10-09 15:50 ` [patch 2/8] mm: write_cache_pages AOP_WRITEPAGE_ACTIVATE fix npiggin
2008-10-10 16:00   ` Miklos Szeredi
2008-10-10 18:29     ` Hugh Dickins
2008-10-11  4:05       ` Nick Piggin [this message]
2008-10-09 15:50 ` [patch 3/8] mm: write_cache_pages writepage error fix npiggin
2008-10-09 15:50 ` [patch 4/8] mm: write_cache_pages type overflow fix npiggin
2008-10-09  8:23   ` Christoph Hellwig
2008-10-09  8:33     ` Nick Piggin
2008-10-10 13:10     ` Theodore Tso
2008-10-10 13:13       ` Christoph Hellwig
2008-10-10 13:37         ` Theodore Tso
2008-10-10 13:48           ` Steven Whitehouse
2008-10-10 14:05             ` Theodore Tso
2008-10-10 14:08               ` Christoph Hellwig
2008-10-10 15:54                 ` Aneesh Kumar K.V
2008-10-10 15:59                   ` Chris Mason
2008-10-10 16:10                   ` Theodore Tso
2008-10-10 16:34                   ` Christoph Hellwig
2008-10-10 13:56           ` Chris Mason
2008-10-09 15:50 ` [patch 5/8] mm: write_cache_pages integrity fix npiggin
2008-10-09 12:52   ` Chris Mason
2008-10-09 13:27     ` Nick Piggin
2008-10-09 13:35       ` Chris Mason
2008-10-09 13:55         ` Nick Piggin
2008-10-09 14:12           ` Chris Mason
2008-10-09 14:21             ` Nick Piggin
2008-10-09 14:39               ` Chris Mason
2008-10-09 14:50                 ` Nick Piggin
2008-10-09 15:16                   ` Chris Mason
2008-10-10  2:40                     ` Nick Piggin
2008-10-09 15:50 ` [patch 6/8] mm: write_cache_pages cleanups npiggin
2008-10-09 14:37   ` Artem Bityutskiy
2008-10-09 15:50 ` [patch 7/8] mm: write_cache_pages optimise page cleaning npiggin
2008-10-09 15:50 ` [patch 8/8] mm: write_cache_pages terminate quickly npiggin

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=200810111505.55812.nickpiggin@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=hugh@veritas.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=miklos@szeredi.hu \
    --cc=mpatocka@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).