Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932372AbWCTR1g (ORCPT ); Mon, 20 Mar 2006 12:27:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932370AbWCTR1g (ORCPT ); Mon, 20 Mar 2006 12:27:36 -0500 Received: from omx1-ext.sgi.com ([192.48.179.11]:26259 "EHLO omx1.americas.sgi.com") by vger.kernel.org with ESMTP id S932372AbWCTR1f (ORCPT ); Mon, 20 Mar 2006 12:27:35 -0500 Date: Mon, 20 Mar 2006 09:27:02 -0800 (PST) From: Christoph Lameter To: Stone Wang cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH][0/8] (Targeting 2.6.17) Posix memory locking and balanced mlock-LRU semantic In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 956 Lines: 22 On Mon, 20 Mar 2006, Stone Wang wrote: > 2. More consistent LRU semantics in Memory Management. > Mlocked pages is placed on a separate LRU list: Wired List. > The pages dont take part in LRU algorithms,for they could never be swapped, > until munlocked. This also implies that dirty bits of the pte for mlocked pages are never checked. Currently light swapping (which is very common) will scan over all pages and move the dirty bits from the pte into struct page. This may take awhile but at least at some point we will write out dirtied pages. The result of not scanning mlocked pages will be that mmapped files will not be updated unless either the process terminates or msync() is called. - 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/