From: Mel Gorman <mgorman@suse.de>
To: Jim Schutt <jaschut@sandia.gov>
Cc: Linux-MM <linux-mm@kvack.org>, Rik van Riel <riel@redhat.com>,
Minchan Kim <minchan@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/5] Improve hugepage allocation success rates under load V3
Date: Tue, 14 Aug 2012 10:23:58 +0100 [thread overview]
Message-ID: <20120814092358.GJ4177@suse.de> (raw)
In-Reply-To: <50296522.2000809@sandia.gov>
On Mon, Aug 13, 2012 at 02:35:46PM -0600, Jim Schutt wrote:
> Hi Mel,
>
> On 08/12/2012 02:22 PM, Mel Gorman wrote:
>
> >
> >I went through the patch again but only found the following which is a
> >weak candidate. Still, can you retest with the following patch on top and
> >CONFIG_PROVE_LOCKING set please?
> >
>
> I've gotten in several hours of testing on this patch with
> no issues at all, and no output from CONFIG_PROVE_LOCKING
> (I'm assuming it would show up on a serial console). So,
> it seems to me this patch has done the trick.
>
Super.
> CPU utilization is staying under control, and write-out rate
> is good.
>
Even better.
> You can add my Tested-by: as you see fit. If you work
> up any refinements and would like me to test, please
> let me know.
>
I'll be adding your Tested-by and I'll keep you cc'd on the series. It'll
look a little different because I'm expect to adjust it slightly to match
Andrew's tree but there should be no major surprises and my expectation is
that testing a -rc kernel after it gets merged is all that is necessary. I'm
planning to backport this to -stable but it'll remain to be seen if I can
convince the relevant maintainers that it should be merged.
Thanks.
--
Mel Gorman
SUSE Labs
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@suse.de>
To: Jim Schutt <jaschut@sandia.gov>
Cc: Linux-MM <linux-mm@kvack.org>, Rik van Riel <riel@redhat.com>,
Minchan Kim <minchan@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/5] Improve hugepage allocation success rates under load V3
Date: Tue, 14 Aug 2012 10:23:58 +0100 [thread overview]
Message-ID: <20120814092358.GJ4177@suse.de> (raw)
In-Reply-To: <50296522.2000809@sandia.gov>
On Mon, Aug 13, 2012 at 02:35:46PM -0600, Jim Schutt wrote:
> Hi Mel,
>
> On 08/12/2012 02:22 PM, Mel Gorman wrote:
>
> >
> >I went through the patch again but only found the following which is a
> >weak candidate. Still, can you retest with the following patch on top and
> >CONFIG_PROVE_LOCKING set please?
> >
>
> I've gotten in several hours of testing on this patch with
> no issues at all, and no output from CONFIG_PROVE_LOCKING
> (I'm assuming it would show up on a serial console). So,
> it seems to me this patch has done the trick.
>
Super.
> CPU utilization is staying under control, and write-out rate
> is good.
>
Even better.
> You can add my Tested-by: as you see fit. If you work
> up any refinements and would like me to test, please
> let me know.
>
I'll be adding your Tested-by and I'll keep you cc'd on the series. It'll
look a little different because I'm expect to adjust it slightly to match
Andrew's tree but there should be no major surprises and my expectation is
that testing a -rc kernel after it gets merged is all that is necessary. I'm
planning to backport this to -stable but it'll remain to be seen if I can
convince the relevant maintainers that it should be merged.
Thanks.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2012-08-14 9:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 13:49 [RFC PATCH 0/5] Improve hugepage allocation success rates under load V3 Mel Gorman
2012-08-09 13:49 ` Mel Gorman
2012-08-09 13:49 ` [PATCH 1/5] mm: compaction: Update comment in try_to_compact_pages Mel Gorman
2012-08-09 13:49 ` Mel Gorman
2012-08-09 13:49 ` [PATCH 2/5] mm: vmscan: Scale number of pages reclaimed by reclaim/compaction based on failures Mel Gorman
2012-08-09 13:49 ` Mel Gorman
2012-08-10 8:49 ` Minchan Kim
2012-08-10 8:49 ` Minchan Kim
2012-08-09 13:49 ` [PATCH 3/5] mm: compaction: Capture a suitable high-order page immediately when it is made available Mel Gorman
2012-08-09 13:49 ` Mel Gorman
2012-08-09 23:35 ` Minchan Kim
2012-08-09 23:35 ` Minchan Kim
2012-08-09 13:49 ` [PATCH 4/5] mm: have order > 0 compaction start off where it left Mel Gorman
2012-08-09 13:49 ` Mel Gorman
2012-08-09 13:49 ` [PATCH 5/5] mm: have order > 0 compaction start near a pageblock with free pages Mel Gorman
2012-08-09 13:49 ` Mel Gorman
2012-08-09 14:36 ` [RFC PATCH 0/5] Improve hugepage allocation success rates under load V3 Jim Schutt
2012-08-09 14:36 ` Jim Schutt
2012-08-09 14:51 ` Mel Gorman
2012-08-09 14:51 ` Mel Gorman
2012-08-09 18:16 ` Jim Schutt
2012-08-09 18:16 ` Jim Schutt
2012-08-09 20:46 ` Mel Gorman
2012-08-09 20:46 ` Mel Gorman
2012-08-09 22:38 ` Jim Schutt
2012-08-09 22:38 ` Jim Schutt
2012-08-10 11:02 ` Mel Gorman
2012-08-10 11:02 ` Mel Gorman
2012-08-10 17:20 ` Jim Schutt
2012-08-10 17:20 ` Jim Schutt
2012-08-12 20:22 ` Mel Gorman
2012-08-12 20:22 ` Mel Gorman
2012-08-13 20:35 ` Jim Schutt
2012-08-13 20:35 ` Jim Schutt
2012-08-14 9:23 ` Mel Gorman [this message]
2012-08-14 9:23 ` Mel Gorman
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=20120814092358.GJ4177@suse.de \
--to=mgorman@suse.de \
--cc=jaschut@sandia.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.