linux-kernel - Re: [RFC 2/8] Don't allow volatile attribute on THP and KSM

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]

Date:	Thu, 03 Jan 2013 08:27:31 -0800
From:	Dave Hansen <dave@...ux.vnet.ibm.com>
To:	Minchan Kim <minchan@...nel.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, Rik van Riel <riel@...hat.com>,
	Hugh Dickins <hughd@...gle.com>,
	Andrea Arcangeli <aarcange@...hat.com>
Subject: Re: [RFC 2/8] Don't allow volatile attribute on THP and KSM

On 01/02/2013 08:28 PM, Minchan Kim wrote:
> VOLATILE imply the the pages in the range isn't working set any more
> so it's pointless that make them to THP/KSM.

One of the points of this implementation is that it be able to preserve
memory contents when there is no pressure.  If those contents happen to
contain a THP/KSM page, and there's no pressure, it seems like the right
thing to do is to leave that memory in place.

It might be a fair thing to do this in order to keep the implementation
more sane at the moment.  But, we should make sure there's some good
text on that in the changelog.

--
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/