From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by nz-out-0102.google.com with SMTP id i11so466416nzi for ; Thu, 08 Jun 2006 13:10:12 -0700 (PDT) Message-ID: <5c49b0ed0606081310q5771e8d1s55acef09b405922b@mail.gmail.com> Date: Thu, 8 Jun 2006 13:10:11 -0700 From: "Nate Diller" Subject: Re: [PATCH] mm: tracking dirty pages -v6 In-Reply-To: <1149770654.4408.71.camel@lappy> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060525135534.20941.91650.sendpatchset@lappy> <1149770654.4408.71.camel@lappy> Sender: owner-linux-mm@kvack.org Return-Path: To: Peter Zijlstra Cc: Hugh Dickins , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andrew Morton , David Howells , Christoph Lameter , Martin Bligh , Nick Piggin , Linus Torvalds List-ID: On 6/8/06, Peter Zijlstra wrote: > > From: Peter Zijlstra > > People expressed the need to track dirty pages in shared mappings. > > Linus outlined the general idea of doing that through making clean > writable pages write-protected and taking the write fault. > > This patch does exactly that, it makes pages in a shared writable > mapping write-protected. On write-fault the pages are marked dirty and > made writable. When the pages get synced with their backing store, the > write-protection is re-instated. Does this mean that processes dirtying pages via mmap are now subject to write throttling? That could dramatically change the performance for tasks with a working set larger than 10% of memory. NATE -- 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