From: Mel Gorman <mel@csn.ul.ie>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Christoph Lameter <cl@linux-foundation.org>,
Adam Litke <agl@us.ibm.com>, Avi Kivity <avi@redhat.com>,
David Rientjes <rientjes@google.com>,
Minchan Kim <minchan.kim@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 13/14] Do not compact within a preferred zone after a compaction failure
Date: Wed, 7 Apr 2010 17:32:18 +0100 [thread overview]
Message-ID: <20100407163217.GV17882@csn.ul.ie> (raw)
In-Reply-To: <20100406170616.7d0f24b1.akpm@linux-foundation.org>
On Tue, Apr 06, 2010 at 05:06:16PM -0700, Andrew Morton wrote:
> On Fri, 2 Apr 2010 17:02:47 +0100
> Mel Gorman <mel@csn.ul.ie> wrote:
>
> > The fragmentation index may indicate that a failure is due to external
> > fragmentation but after a compaction run completes, it is still possible
> > for an allocation to fail. There are two obvious reasons as to why
> >
> > o Page migration cannot move all pages so fragmentation remains
> > o A suitable page may exist but watermarks are not met
> >
> > In the event of compaction followed by an allocation failure, this patch
> > defers further compaction in the zone for a period of time. The zone that
> > is deferred is the first zone in the zonelist - i.e. the preferred zone.
> > To defer compaction in the other zones, the information would need to be
> > stored in the zonelist or implemented similar to the zonelist_cache.
> > This would impact the fast-paths and is not justified at this time.
> >
>
> Your patch, it sucks!
>
> > ---
> > include/linux/compaction.h | 35 +++++++++++++++++++++++++++++++++++
> > include/linux/mmzone.h | 7 +++++++
> > mm/page_alloc.c | 5 ++++-
> > 3 files changed, 46 insertions(+), 1 deletions(-)
> >
> > diff --git a/include/linux/compaction.h b/include/linux/compaction.h
> > index ae98afc..2a02719 100644
> > --- a/include/linux/compaction.h
> > +++ b/include/linux/compaction.h
> > @@ -18,6 +18,32 @@ extern int sysctl_extfrag_handler(struct ctl_table *table, int write,
> > extern int fragmentation_index(struct zone *zone, unsigned int order);
> > extern unsigned long try_to_compact_pages(struct zonelist *zonelist,
> > int order, gfp_t gfp_mask, nodemask_t *mask);
> > +
> > +/* defer_compaction - Do not compact within a zone until a given time */
> > +static inline void defer_compaction(struct zone *zone, unsigned long resume)
> > +{
> > + /*
> > + * This function is called when compaction fails to result in a page
> > + * allocation success. This is somewhat unsatisfactory as the failure
> > + * to compact has nothing to do with time and everything to do with
> > + * the requested order, the number of free pages and watermarks. How
> > + * to wait on that is more unclear, but the answer would apply to
> > + * other areas where the VM waits based on time.
> > + */
>
> c'mon, let's not make this rod for our backs.
>
> The "A suitable page may exist but watermarks are not met" case can be
> addressed by testing the watermarks up-front, surely?
>
Nope, because the number of pages free at each order changes before and
after compaction and you don't know by how much in advance. It wouldn't
be appropriate to assume perfect compaction because unmovable and
reclaimable pages are free.
> I bet the "Page migration cannot move all pages so fragmentation
> remains" case can be addressed by setting some metric in the zone, and
> suitably modifying that as a result on ongoing activity.
> To tell the
> zone "hey, compaction migth be worth trying now". that sucks too, but not
> so much.
>
> Or something. Putting a wallclock-based throttle on it like this
> really does reduce the usefulness of the whole feature.
>
When it gets down to it, this patch was about paranoia. If the
heuristics on compaction-avoidance didn't work out, I didn't want
compaction to keep pounding.
That said, this patch would also hide the bug report telling us this happened
and was a mistake. A bug report detailing high oprofile usage in compaction
will be much easier to come across than a report on defer_compaction()
being called too often.
Please drop this patch.
> Internet: "My application works OK on a hard disk but fails when I use an SSD!".
>
> akpm: "Tell Mel!"
>
Mel is in and he is listening.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
--
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:[~2010-04-07 16:32 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 16:02 [PATCH 0/14] Memory Compaction v7 Mel Gorman
2010-04-02 16:02 ` [PATCH 01/14] mm,migration: Take a reference to the anon_vma before migrating Mel Gorman
2010-04-07 0:05 ` Andrew Morton
2010-04-07 9:56 ` Mel Gorman
2010-04-02 16:02 ` [PATCH 02/14] mm,migration: Do not try to migrate unmapped anonymous pages Mel Gorman
2010-04-02 16:02 ` [PATCH 03/14] mm: Share the anon_vma ref counts between KSM and page migration Mel Gorman
2010-04-07 0:05 ` Andrew Morton
2010-04-07 0:10 ` Rik van Riel
2010-04-07 10:01 ` Mel Gorman
2010-04-02 16:02 ` [PATCH 04/14] Allow CONFIG_MIGRATION to be set without CONFIG_NUMA or memory hot-remove Mel Gorman
2010-04-07 0:05 ` Andrew Morton
2010-04-07 10:22 ` Mel Gorman
2010-04-02 16:02 ` [PATCH 05/14] Export unusable free space index via /proc/unusable_index Mel Gorman
2010-04-07 0:05 ` Andrew Morton
2010-04-07 10:35 ` Mel Gorman
2010-04-13 12:42 ` Mel Gorman
2010-04-02 16:02 ` [PATCH 06/14] Export fragmentation index via /proc/extfrag_index Mel Gorman
2010-04-07 0:05 ` Andrew Morton
2010-04-07 10:46 ` Mel Gorman
2010-04-13 12:43 ` Mel Gorman
2010-04-02 16:02 ` [PATCH 07/14] Move definition for LRU isolation modes to a header Mel Gorman
2010-04-02 16:02 ` [PATCH 08/14] Memory compaction core Mel Gorman
2010-04-07 0:05 ` Andrew Morton
2010-04-07 15:21 ` Mel Gorman
2010-04-08 16:59 ` Mel Gorman
2010-04-08 17:06 ` Andrea Arcangeli
2010-04-02 16:02 ` [PATCH 09/14] Add /proc trigger for memory compaction Mel Gorman
2010-04-07 0:05 ` Andrew Morton
2010-04-07 15:39 ` Mel Gorman
2010-04-07 18:27 ` Mel Gorman
2010-04-02 16:02 ` [PATCH 10/14] Add /sys trigger for per-node " Mel Gorman
2010-04-07 0:05 ` Andrew Morton
2010-04-07 0:31 ` KAMEZAWA Hiroyuki
2010-04-06 21:56 ` Andrew Morton
2010-04-07 1:19 ` KAMEZAWA Hiroyuki
2010-04-07 15:42 ` Mel Gorman
2010-04-02 16:02 ` [PATCH 11/14] Direct compact when a high-order allocation fails Mel Gorman
2010-04-07 0:06 ` Andrew Morton
2010-04-07 16:06 ` Mel Gorman
2010-04-07 18:29 ` Mel Gorman
2010-04-02 16:02 ` [PATCH 12/14] Add a tunable that decides when memory should be compacted and when it should be reclaimed Mel Gorman
2010-04-07 0:06 ` Andrew Morton
2010-04-07 16:11 ` Mel Gorman
2010-04-02 16:02 ` [PATCH 13/14] Do not compact within a preferred zone after a compaction failure Mel Gorman
2010-04-07 0:06 ` Andrew Morton
2010-04-07 0:55 ` Andrea Arcangeli
2010-04-07 16:32 ` Mel Gorman [this message]
2010-04-02 16:02 ` [PATCH 14/14] mm,migration: Allow the migration of PageSwapCache pages Mel Gorman
2010-04-06 6:54 ` KAMEZAWA Hiroyuki
2010-04-06 15:37 ` Minchan Kim
2010-04-07 0:06 ` Andrew Morton
2010-04-07 16:49 ` Mel Gorman
2010-04-06 14:47 ` [PATCH 0/14] Memory Compaction v7 Tarkan Erimer
2010-04-06 15:00 ` Mel Gorman
2010-04-06 15:03 ` Tarkan Erimer
-- strict thread matches above, loose matches on Subject: below --
2010-03-30 9:14 [PATCH 0/14] Memory Compaction v6 Mel Gorman
2010-03-30 9:14 ` [PATCH 13/14] Do not compact within a preferred zone after a compaction failure 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=20100407163217.GV17882@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=aarcange@redhat.com \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=cl@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.com \
--cc=rientjes@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;
as well as URLs for NNTP newsgroup(s).