linux-kernel - Re: [RFC][PATCH] Anonymous shared memory (ashmem) subsystem

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.00.1107190931450.1199@router.home>
Date:	Tue, 19 Jul 2011 09:33:56 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	John Stultz <john.stultz@...aro.org>
cc:	LKML <linux-kernel@...r.kernel.org>,
	Robert Love <rlove@...gle.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Hugh Dickins <hughd@...gle.com>, Mel Gorman <mel@....ul.ie>,
	Dave Hansen <dave@...ux.vnet.ibm.com>,
	Rik van Riel <riel@...hat.com>,
	Eric Anholt <eric@...olt.net>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [RFC][PATCH] Anonymous shared memory (ashmem) subsystem

On Mon, 18 Jul 2011, John Stultz wrote:

> Additionally, ashmem introduces the concept of page pinning. Pinned pages (the
> default) behave like any anonymous memory. Unpinned pages are available to the
> kernel for eviction during VM pressure. When repinning the pages, the return
> value instructs user-space as to any eviction. In this manner, user-space
> processes may implement caching and similar resource management that
> efficiently integrates with kernel memory management.

Memory locking (mlock) may be a better term to use here. mlock prevents
eviction. Page pinning also prevents the movement of the pages in memory
(as needed by page migration, compaction etc).

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