Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751674Ab3HTPbg (ORCPT ); Tue, 20 Aug 2013 11:31:36 -0400 Received: from mail-lb0-f174.google.com ([209.85.217.174]:60628 "EHLO mail-lb0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751289Ab3HTPbf (ORCPT ); Tue, 20 Aug 2013 11:31:35 -0400 Date: Tue, 20 Aug 2013 19:31:32 +0400 From: Cyrill Gorcunov To: Andrew Morton Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Andy Lutomirski , Pavel Emelyanov , Matt Mackall , Xiao Guangrong , Marcelo Tosatti , KOSAKI Motohiro , Stephen Rothwell , Peter Zijlstra , "Aneesh Kumar K.V" Subject: [PATCH -mm] docs: Document soft dirty behaviour for freshly created memory regions Message-ID: <20130820153132.GK18673@moon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1823 Lines: 38 Signed-off-by: Cyrill Gorcunov Cc: Pavel Emelyanov Cc: Andy Lutomirski Cc: Andrew Morton Cc: Matt Mackall Cc: Xiao Guangrong Cc: Marcelo Tosatti Cc: KOSAKI Motohiro Cc: Stephen Rothwell Cc: Peter Zijlstra Cc: "Aneesh Kumar K.V" --- Documentation/vm/soft-dirty.txt | 7 +++++++ 1 file changed, 7 insertions(+) Index: linux-2.6.git/Documentation/vm/soft-dirty.txt =================================================================== --- linux-2.6.git.orig/Documentation/vm/soft-dirty.txt +++ linux-2.6.git/Documentation/vm/soft-dirty.txt @@ -28,6 +28,13 @@ This is so, since the pages are still ma the kernel does is finds this fact out and puts both writable and soft-dirty bits on the PTE. + While in most cases tracking memory changes by #PF-s is more than enough +there is still a scenario when we can loose soft dirty bit -- a task does +unmap previously mapped memory region and then maps new one exactly at the +same place. When unmap called the kernel internally clears PTEs values +including soft dirty bit. To notify user space application about such +memory region renewal the kernel always mark new memory regions (and +expanded regions) as soft dirtified. This feature is actively used by the checkpoint-restore project. You can find more details about it on http://criu.org -- 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/