From: Huang Shijie <b32955@freescale.com>
To: Mel Gorman <mgorman@suse.de>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm/compaction : check the watermark when cc->order is -1
Date: Thu, 5 Jan 2012 19:21:20 +0800 [thread overview]
Message-ID: <4F0587B0.8000006@freescale.com> (raw)
In-Reply-To: <20120105105308.GF28031@suse.de>
> On Sat, Dec 31, 2011 at 02:18:43PM +0800, Huang Shijie wrote:
>> We get cc->order is -1 when user echos to /proc/sys/vm/compact_memory.
>> In this case, we should check that if we have enough pages for
>> the compaction in the zone.
>>
>> If we do not check this, in our MX6Q board(arm), i ever observed
>> COMPACT_CLUSTER_MAX pages were compaction failed in per migrate_pages().
>> That's mean we can not alloc any pages by the free scanner in the zone.
>>
>> This patch checks the watermark to avoid this problem.
>>
>> Signed-off-by: Huang Shijie<b32955@freescale.com>
>> ---
>> mm/compaction.c | 14 ++++++++++++--
>> 1 files changed, 12 insertions(+), 2 deletions(-)
>>
>> diff --git a/mm/compaction.c b/mm/compaction.c
>> index 899d956..0f12cc9 100644
>> --- a/mm/compaction.c
>> +++ b/mm/compaction.c
>> @@ -442,8 +442,13 @@ static int compact_finished(struct zone *zone,
>> * order == -1 is expected when compacting via
>> * /proc/sys/vm/compact_memory
>> */
>> - if (cc->order == -1)
>> + if (cc->order == -1) {
>> + /* Check if we have enough pages now. */
>> + watermark = low_wmark_pages(zone) + COMPACT_CLUSTER_MAX * 2;
>> + if (!zone_watermark_ok(zone, 0, watermark, 0, 0))
>> + return COMPACT_SKIPPED;
>> return COMPACT_CONTINUE;
>> + }
>>
> We already do the watermark check in compact_finished. Would moving
> the cc->order == -1 check below it not be functionally equivalent? This
Now, I think these code for compact_finish() is not needed. These lines
can be removed.
The watermark check in the compaction_suitable() is enough to avoid the
problem.
Huang Shijie
> would be preferable to duplicating the code for the watermark check.
>
> Same for the second check in your patch.
>
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2012-01-05 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 6:18 [PATCH] mm/compaction : check the watermark when cc->order is -1 Huang Shijie
2012-01-05 10:53 ` Mel Gorman
2012-01-05 11:21 ` Huang Shijie [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=4F0587B0.8000006@freescale.com \
--to=b32955@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/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).