From: Rik van Riel <riel@redhat.com>
To: David Rientjes <rientjes@google.com>, 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>, Michal Hocko <mhocko@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V5] Allow compaction of unevictable pages
Date: Fri, 13 Mar 2015 19:43:45 -0400 [thread overview]
Message-ID: <55037631.3010402@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1503131613560.7827@chino.kir.corp.google.com>
On 03/13/2015 07:18 PM, David Rientjes wrote:
> On Fri, 13 Mar 2015, Eric B Munson wrote:
>
>>>> --- a/mm/compaction.c
>>>> +++ b/mm/compaction.c
>>>> @@ -1046,6 +1046,8 @@ typedef enum {
>>>> ISOLATE_SUCCESS, /* Pages isolated, migrate */
>>>> } isolate_migrate_t;
>>>>
>>>> +int sysctl_compact_unevictable;
>>>> +
>>>> /*
>>>> * Isolate all pages that can be migrated from the first suitable block,
>>>> * starting at the block pointed to by the migrate scanner pfn within
>>>
>>> I suspect that the use cases where users absolutely do not want
>>> unevictable pages migrated are special cases, and it may make
>>> sense to enable sysctl_compact_unevictable by default.
>>
>> Given that sysctl_compact_unevictable=0 is the way the kernel behaves
>> now and the push back against always enabling compaction on unevictable
>> pages, I left the default to be the behavior as it is today. I agree
>> that this is likely the minority case, but I'd really like Peter Z or
>> someone else from real time to say that they are okay with the default
>> changing.
>>
>
> It would be really disappointing to not enable this by default for !rt
> kernels. We haven't migrated mlocked pages in the past by way of memory
> compaction because it can theoretically result in consistent minor page
> faults, but I haven't yet heard a !rt objection to enabling this.
>
> If the rt patchset is going to carry a patch to disable this
It does not have to carry a patch to disable something that can be
disabled at run time.
The smaller the realtime patchset has to be, the better.
--
All rights reversed
next prev parent reply other threads:[~2015-03-13 23:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 17:26 [PATCH V5] Allow compaction of unevictable pages Eric B Munson
2015-03-13 18:56 ` Rik van Riel
2015-03-13 19:09 ` Eric B Munson
2015-03-13 20:19 ` Michal Hocko
2015-03-16 10:14 ` Vlastimil Babka
2015-03-16 13:49 ` Eric B Munson
2015-03-18 14:40 ` Vlastimil Babka
2015-03-18 15:40 ` Steven Rostedt
2015-03-13 23:18 ` David Rientjes
2015-03-13 23:43 ` Rik van Riel [this message]
2015-03-16 15:39 ` Christoph Lameter
2015-03-13 20:02 ` Michal Hocko
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=55037631.3010402@redhat.com \
--to=riel@redhat.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=mhocko@suse.cz \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--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;
as well as URLs for NNTP newsgroup(s).