linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux.com>
To: David Rientjes <rientjes@google.com>
Cc: Eric B Munson <emunson@akamai.com>,
	Rik van Riel <riel@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	Thomas Gleixner <tglx@linutronix.de>,
	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: Mon, 16 Mar 2015 10:39:42 -0500 (CDT)	[thread overview]
Message-ID: <alpine.DEB.2.11.1503161036160.32513@gentwo.org> (raw)
In-Reply-To: <alpine.DEB.2.10.1503131613560.7827@chino.kir.corp.google.com>

On Fri, 13 Mar 2015, David Rientjes wrote:

> 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, then the
> question arises: why not just carry an ISOLATE_UNEVICTABLE patch instead?
> I think you've done the due diligence required to allow this to be
> disabled at any time in a very easy way from userspace by the new tunable.
> I think it should be enabled and I'd be very surprised to hear any other
> objection about it other than it's different from the status quo.

Compaction can alrady be disabled and thus you can also disable migration
of mlocked pages. In general low latency requires that no expensive kernel
processing is being done. Thus the rest of compaction processing also
needs to be disabled. That means that allowing compaction handling
mlocked pages would be ok. RT loads and low latency configurations (like
my environment) will selective disable compaction to avoid creating
additional latencies. This could be done only for specific nodes and
processors if necessary.



  parent reply	other threads:[~2015-03-16 15:39 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
2015-03-16 15:39       ` Christoph Lameter [this message]
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=alpine.DEB.2.11.1503161036160.32513@gentwo.org \
    --to=cl@linux.com \
    --cc=akpm@linux-foundation.org \
    --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=riel@redhat.com \
    --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).