From: David Rientjes <rientjes@google.com>
To: Minchan Kim <minchan@kernel.org>
Cc: Rik van Riel <riel@redhat.com>, Jim Schutt <jaschut@sandia.gov>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mel@csn.ul.ie>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: excessive CPU utilization by isolate_freepages?
Date: Wed, 27 Jun 2012 18:06:59 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1206271803280.10830@chino.kir.corp.google.com> (raw)
In-Reply-To: <4FEBAC42.3030800@kernel.org>
On Thu, 28 Jun 2012, Minchan Kim wrote:
> >>> > > https://lkml.org/lkml/2012/6/21/30
> >> >
> > Not sure if Jim is using memcg; if not, then this won't be helpful.
> >
>
>
> It doesn't related to memcg.
> if compaction_alloc can't find suitable migration target, it returns NULL.
> Then, migrate_pages should be exit.
>
If isolate_freepages() is going to fail, then this zone should have been
skipped when checking for compaction_suitable(). In Jim's perf output,
compaction_suitable() returns COMPACT_CONTINUE for a transparent hugepage.
Why is zone_watermark_ok(zone, 0 low_wmark + 1024, 0, 0) succeeding if
isolate_freepages() is going to fail?
--
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:[~2012-06-28 1:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 21:59 Jim Schutt
2012-06-27 22:35 ` Mark Nelson
2012-06-27 23:59 ` Minchan Kim
2012-06-28 0:28 ` Rik van Riel
2012-06-28 0:52 ` David Rientjes
2012-06-28 0:58 ` Minchan Kim
2012-06-28 1:06 ` David Rientjes [this message]
2012-06-28 1:18 ` Minchan Kim
2012-06-28 1:13 ` Rik van Riel
2012-06-28 0:55 ` Minchan Kim
2012-06-28 11:36 ` Mel Gorman
2012-06-28 15:30 ` Jim Schutt
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.DEB.2.00.1206271803280.10830@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=ceph-devel@vger.kernel.org \
--cc=jaschut@sandia.gov \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox