From: Hugh Dickins <hughd@google.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Paul Mackerras <paulus@ozlabs.org>,
linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org
Subject: Re: Problems with swapping in v4.5-rc on POWER
Date: Fri, 26 Feb 2016 02:04:49 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.11.1602260157430.10399@eggly.anvils> (raw)
In-Reply-To: <alpine.LSU.2.11.1602251322130.8063@eggly.anvils>
On Thu, 25 Feb 2016, Hugh Dickins wrote:
> On Wed, 24 Feb 2016, Hugh Dickins wrote:
> > On Thu, 25 Feb 2016, Aneesh Kumar K.V wrote:
> > >
> > > Can you test the impact of the merge listed below ?(ie, revert the merge and see if
> > > we can reproduce and also verify with merge applied). This will give us a
> > > set of commits to look closer. We had quiet a lot of page table
> > > related changes going in this merge window.
> > >
> > > f689b742f217b2ffe7 ("Pull powerpc updates from Michael Ellerman:")
> > >
> > > That is the merge commit that added _PAGE_PTE.
> >
> > Another experiment running on it at the moment, I'd like to give that
> > a few more hours, and then will try the revert you suggest. But does
> > that merge revert cleanly, did you try? I'm afraid of interactions,
> > whether obvious or subtle, with the THP refcounting rework. Oh, since
> > I don't have THP configured on, maybe I can ignore any issues from that.
>
> That revert worked painlessly, only a very few and simple conflicts,
> I ran that under load for 12 hours, no problem seen.
>
> I've now checked out an f689b742 tree and started on that, just to
> confirm that it fails fairly quickly I hope; and will then proceed
> to git bisect, giving that as bad and 37cea93b as good.
>
> Given the uncertainty of whether 12 hours is really long enough to be
> sure, and perhaps difficulties along the way, I don't rate my chances
> of a reliable bisection higher than 60%, but we'll see.
I'm sure you won't want a breathless report from me on each bisection
step, but I ought to report that: contrary to our expectations, the
f689b742 survived without error for 12 hours, so appears to be good.
I'll bisect between there and v4.5-rc1.
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>
next prev parent reply other threads:[~2016-02-26 10:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 2:10 Hugh Dickins
2016-02-25 4:12 ` Michael Ellerman
2016-02-25 5:36 ` Hugh Dickins
2016-02-25 4:52 ` Aneesh Kumar K.V
2016-02-25 5:43 ` Hugh Dickins
2016-02-25 21:35 ` Hugh Dickins
2016-02-26 10:04 ` Hugh Dickins [this message]
2016-03-02 20:49 ` Hugh Dickins
2016-03-03 5:51 ` Michael Ellerman
2016-03-04 17:58 ` Hugh Dickins
2016-03-07 3:00 ` Michael Ellerman
2016-03-08 11:49 ` Hugh Dickins
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=alpine.LSU.2.11.1602260157430.10399@eggly.anvils \
--to=hughd@google.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@ozlabs.org \
/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