linux-kernel - Re: [RFC] mlock: release mmap

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: <20101124085451.7BE5.A69D9226@jp.fujitsu.com>
Date:	Wed, 24 Nov 2010 08:57:56 +0900 (JST)
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	Michel Lespinasse <walken@...gle.com>
Cc:	kosaki.motohiro@...fujitsu.com,
	Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org,
	Hugh Dickins <hugh.dickins@...cali.co.uk>,
	Nick Piggin <npiggin@...nel.dk>, Rik van Riel <riel@...hat.com>
Subject: Re: [RFC] mlock: release mmap_sem every 256 faulted pages

> > A more compelling description of why this problem needs addressing
> > would help things along.
> 
> Oh my. It's probably not too useful for desktops, where such large
> mlocks are hopefully uncommon.
> 
> At google we have many applications that serve data from memory and
> don't want to allow for disk latencies. Some of the simpler ones use
> mlock (though there are other ways - anon memory running with swap
> disabled is a surprisingly popular choice).
> 
> Kosaki is also showing interest in mlock, though I'm not sure what his
> use case is.

I don't have any solid use case. Usually server app only do mlock anonymous memory.
But, I haven't found any negative effect in your proposal, therefore I hope to help
your effort as I always do when the proposal don't have negative impact.



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