From mboxrd@z Thu Jan 1 00:00:00 1970 From: KOSAKI Motohiro Subject: Re: [PATCH v5] add MAP_UNLOCKED mmap flag Date: Thu, 14 Jan 2010 09:31:03 +0900 (JST) Message-ID: <20100114092845.D719.A69D9226@jp.fujitsu.com> References: <20100113093119.GT7549@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20100113093119.GT7549@redhat.com> Sender: owner-linux-mm@kvack.org To: Gleb Natapov Cc: kosaki.motohiro@jp.fujitsu.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, akpm@linux-foundation.org List-Id: linux-api@vger.kernel.org > If application does mlockall(MCL_FUTURE) it is no longer possible to mmap > file bigger than main memory or allocate big area of anonymous memory > in a thread safe manner. Sometimes it is desirable to lock everything > related to program execution into memory, but still be able to mmap > big file or allocate huge amount of memory and allow OS to swap them on > demand. MAP_UNLOCKED allows to do that. > > Signed-off-by: Gleb Natapov > --- > > I get reports that people find this useful, so resending. This description is still wrong. It doesn't describe why this patch is useful. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org