From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail143.messagelabs.com (mail143.messagelabs.com [216.82.254.35]) by kanga.kvack.org (Postfix) with ESMTP id 84D326B0071 for ; Wed, 13 Jan 2010 12:31:59 -0500 (EST) Date: Wed, 13 Jan 2010 09:31:52 -0800 From: Chris Wright Subject: Re: [PATCH v5] add MAP_UNLOCKED mmap flag Message-ID: <20100113173152.GA2666@sequoia.sous-sol.org> References: <20100113093119.GT7549@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100113093119.GT7549@redhat.com> Sender: owner-linux-mm@kvack.org To: Gleb Natapov Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, akpm@linux-foundation.org List-ID: * Gleb Natapov (gleb@redhat.com) wrote: > 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 Looks good to me. Acked-by: Chris Wright thanks, -chris -- 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