lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1503161036160.32513@gentwo.org>
Date:	Mon, 16 Mar 2015 10:39:42 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	David Rientjes <rientjes@...gle.com>
cc:	Eric B Munson <emunson@...mai.com>, Rik van Riel <riel@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Vlastimil Babka <vbabka@...e.cz>,
	Thomas Gleixner <tglx@...utronix.de>,
	Peter Zijlstra <peterz@...radead.org>,
	Mel Gorman <mgorman@...e.de>, Michal Hocko <mhocko@...e.cz>,
	linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V5] Allow compaction of unevictable pages

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.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ