From: David Rientjes <rientjes@google.com>
To: Eric B Munson <emunson@akamai.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Thomas Gleixner <tglx@linutronix.de>,
Christoph Lameter <cl@linux.com>,
Peter Zijlstra <peterz@infradead.org>,
Mel Gorman <mgorman@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Allow compaction of unevictable pages
Date: Fri, 6 Mar 2015 13:07:02 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.10.1503061301500.10330@chino.kir.corp.google.com> (raw)
In-Reply-To: <1425667287-30841-1-git-send-email-emunson@akamai.com>
On Fri, 6 Mar 2015, Eric B Munson wrote:
> diff --git a/mm/compaction.c b/mm/compaction.c
> index 8c0d945..33c81e1 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -1056,7 +1056,7 @@ static isolate_migrate_t isolate_migratepages(struct zone *zone,
> {
> unsigned long low_pfn, end_pfn;
> struct page *page;
> - const isolate_mode_t isolate_mode =
> + const isolate_mode_t isolate_mode = ISOLATE_UNEVICTABLE |
> (cc->mode == MIGRATE_ASYNC ? ISOLATE_ASYNC_MIGRATE : 0);
>
> /*
I agree that memory compaction should be isolating and migrating
unevictable memory for better results, and we have been running with a
similar patch internally for about a year for the same purpose as you,
higher probability of allocating hugepages.
This would be better off removing the notion of ISOLATE_UNEVICTABLE
entirely, however, since CMA and now memory compaction would be using it,
so the check in __isolate_lru_page() is no longer necessary. Has the
added bonus of removing about 10 lines of soure code.
--
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:[~2015-03-06 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 18:41 Eric B Munson
2015-03-06 21:07 ` David Rientjes [this message]
2015-03-09 17:05 ` Eric B Munson
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.10.1503061301500.10330@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=emunson@akamai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
/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