From: Mel Gorman <mel@csn.ul.ie>
To: Michel Lespinasse <walken@google.com>
Cc: Rik van Riel <riel@redhat.com>,
Wu Fengguang <fengguang.wu@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-arch@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Ying Han <yinghan@google.com>,
Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: [BUG] Commit d065bd81 severely regresses huge page allocation success rates
Date: Thu, 11 Nov 2010 14:25:27 +0000 [thread overview]
Message-ID: <20101111142527.GG19679@csn.ul.ie> (raw)
In-Reply-To: <AANLkTinxYntXjK7V8W3+3j7m0xQUVpB1eeysSE0ifO1k@mail.gmail.com>
On Thu, Nov 11, 2010 at 04:25:00AM -0800, Michel Lespinasse wrote:
> On Thu, Nov 11, 2010 at 4:15 AM, Mel Gorman <mel@csn.ul.ie> wrote:
> > When testing 2.6.37-rc1, I noticed that huge page allocation success
> > rates were severely impaired. Bisection showed that commit [d065bd81: mm:
> > retry page fault when blocking on disk transfer] was the biggest factor.
> > Reverting the patch confirmed this. Here are the results of a high-order
> > allocation stress test. The vanilla kernel is 2.6.37-rc1 and the revert
> > kernel has this commit removed with minor conflicts cleaned up.
> [...]
> > I have not digested what the patch is doing but am reporting it in case
> > people familiar with the patch spot the problem quickly.
>
> There was a bug in that commit, which was fixed in
> d88c0922fa0e2c021a028b310a641126c6d4b7dc
>
> I think this may explain the issue; compaction won't work well if
> extra references are kept :/
>
Reclaim would not work either as it is effectively a leak.
> Can you check that this indeed solves your test case ?
>
It does. Thanks very much.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
prev parent reply other threads:[~2010-11-11 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 12:15 [BUG] Commit d065bd81 severely regresses huge page allocation success rates Mel Gorman
2010-11-11 12:15 ` Mel Gorman
2010-11-11 12:25 ` Michel Lespinasse
2010-11-11 14:25 ` Mel Gorman [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=20101111142527.GG19679@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=walken@google.com \
--cc=yinghan@google.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