Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932213AbWCUHK5 (ORCPT ); Tue, 21 Mar 2006 02:10:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932271AbWCUHK5 (ORCPT ); Tue, 21 Mar 2006 02:10:57 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:8101 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S932213AbWCUHK4 (ORCPT ); Tue, 21 Mar 2006 02:10:56 -0500 Subject: Re: [PATCH][0/8] (Targeting 2.6.17) Posix memory locking and balanced mlock-LRU semantic From: Arjan van de Ven To: Nate Diller Cc: Stone Wang , akpm@osdl.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org In-Reply-To: <5c49b0ed0603201552j58150a18lbf4d0a9b0406d175@mail.gmail.com> References: <1142862078.3114.47.camel@laptopd505.fenrus.org> <5c49b0ed0603201552j58150a18lbf4d0a9b0406d175@mail.gmail.com> Content-Type: text/plain Date: Tue, 21 Mar 2006 08:10:52 +0100 Message-Id: <1142925053.3077.6.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1363 Lines: 31 On Mon, 2006-03-20 at 15:52 -0800, Nate Diller wrote: > On 3/20/06, Arjan van de Ven wrote: > > > 1. Posix mlock/munlock/mlockall/munlockall. > > > Get mlock/munlock/mlockall/munlockall to Posix definiton: transaction-like, > > > just as described in the manpage(2) of mlock/munlock/mlockall/munlockall. > > > Thus users of mlock system call series will always have an clear map of > > > mlocked areas. > > > 2. More consistent LRU semantics in Memory Management. > > > Mlocked pages is placed on a separate LRU list: Wired List. > > > > please give this a more logical name, such as mlocked list or pinned > > list > > Shaoping, thanks for doing this work, it is something I have been > thinking about for the past few weeks. It's especially nice to be > able to see how many pages are pinned in this manner. > > Might I suggest calling it the long_term_pinned list? It also might > be worth putting ramdisk pages on this list, since they cannot be > written out in response to memory pressure. This would eliminate the > need for AOP_WRITEPAGE_ACTIVATE. I like that idea - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/