public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: riel@redhat.com, Lee.Schermerhorn@hp.com,
	kosaki.motohiro@jp.fujitsu.com, nickpiggin@yahoo.com.au,
	linux-kernel@vger.kernel.org
Subject: Re: [METAPATCH] mmotm: fix split-lru bisectability
Date: Wed, 15 Oct 2008 14:39:15 -0700	[thread overview]
Message-ID: <20081015143915.cc4395ed.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0810140125550.29541@blonde.site>

On Tue, 14 Oct 2008 01:32:18 +0100 (BST)
Hugh Dickins <hugh@veritas.com> wrote:

> There's an unbisectable 24-patch extent in the mmotm series, from
> define-page_file_cache-function to mlock-mlocked-pages-are-unevictable-fix:
> unbisectable because startup gets swamped by "Bad page state" messages
> (with three unrelated build errors and their fixes along the way).
> 
> These bad page states come from when Linus fasttracked the PAGE_FLAGS
> "cleanup" into 2.6.26, conflicting with PG_swapbacked patches already
> queued in -mm, and then the merge was botched.  We fixed up the end
> result at the time, but never got around to fixing the intermediates.
> It would be regrettable if this unbisectability were preserved in git.
> 
> To apply this metapatch, cd into mmotm's broken-out or patches directory
> (before define-page_file_cache-function has been applied), move series
> file there if it's kept elsewhere, apply metapatch with "patch -p1" (one
> file is deleted from series), then move back series file if necessary.
> 
> Based on mmotm .DATE=2008-10-10-19-22.  Doesn't bother to update the
> diffstats: I've tried to keep the diffs minimal, without all the noise
> which a quilt refresh here would have added.  So oddly I'm commenting
> out NORECL_PGRESCUED and NORECL_PGCULLED in one patch, then removing
> those lines in their fix patch - hmm, shouldn't they have got defined
> eventually, and that code restored?  End result is the same as mmotm,
> except that KOSAKI-San's page_referenced() args fix is included.
> 
> I'm pleased to say that checkpatch.pl reports that this metapatch
> has no obvious style problems and is ready for submission :-)
> 
> Signed-off-by: Hugh Dickins <hugh@veritas.com>
> ---
> 
>  series                                                       |    1 
>  define-page_file_cache-function.patch                        |   26 +++++--
>  vmscan-fix-pagecache-reclaim-referenced-bit-check-fix.patch  |    5 -
>  unevictable-lru-infrastructure.patch                         |   12 +--
>  unevictable-lru-infrastructure-defer-vm-event-counting.patch |    4 -
>  mlock-mlocked-pages-are-unevictable.patch                    |   24 -------
>  mlock-mlocked-pages-are-unevictable-fix.patch                |   33 ----------
>  7 files changed, 32 insertions(+), 73 deletions(-)

OK, thanks, I did that.  Fingers crossed..

      reply	other threads:[~2008-10-15 21:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14  0:32 [METAPATCH] mmotm: fix split-lru bisectability Hugh Dickins
2008-10-15 21:39 ` Andrew Morton [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=20081015143915.cc4395ed.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=hugh@veritas.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=riel@redhat.com \
    /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