All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Andy Lutomirski <luto@amacapital.net>,
	Pavel Emelyanov <xemul@parallels.com>,
	Matt Mackall <mpm@selenic.com>,
	Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Peter Zijlstra <peterz@infradead.org>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH -mm] docs: Document soft dirty behaviour for freshly created memory regions
Date: Tue, 20 Aug 2013 09:57:38 -0700	[thread overview]
Message-ID: <5213A002.7020408@infradead.org> (raw)
In-Reply-To: <20130820153132.GK18673@moon>

On 08/20/13 08:31, Cyrill Gorcunov wrote:
> Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org>
> Cc: Pavel Emelyanov <xemul@parallels.com>
> Cc: Andy Lutomirski <luto@amacapital.net>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Matt Mackall <mpm@selenic.com>
> Cc: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
> Cc: Marcelo Tosatti <mtosatti@redhat.com>
> Cc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
> ---
>  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
                                                                       enough,

> +there is still a scenario when we can loose soft dirty bit -- a task does
                                         lose soft dirty bits -- a task

> +unmap previously mapped memory region and then maps new one exactly at the

   unmaps a previously mapped memory region and then maps a new one at exactly the

> +same place. When unmap called the kernel internally clears PTEs values

               When unmap is called, the kernel internally clears PTE values

> +including soft dirty bit. To notify user space application about such
                        bits.

> +memory region renewal the kernel always mark new memory regions (and
                                           marks

> +expanded regions) as soft dirtified.

or:                  as soft dirty.

>  
>    This feature is actively used by the checkpoint-restore project. You
>  can find more details about it on http://criu.org
> --


-- 
~Randy

--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@infradead.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Andy Lutomirski <luto@amacapital.net>,
	Pavel Emelyanov <xemul@parallels.com>,
	Matt Mackall <mpm@selenic.com>,
	Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Peter Zijlstra <peterz@infradead.org>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH -mm] docs: Document soft dirty behaviour for freshly created memory regions
Date: Tue, 20 Aug 2013 09:57:38 -0700	[thread overview]
Message-ID: <5213A002.7020408@infradead.org> (raw)
In-Reply-To: <20130820153132.GK18673@moon>

On 08/20/13 08:31, Cyrill Gorcunov wrote:
> Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org>
> Cc: Pavel Emelyanov <xemul@parallels.com>
> Cc: Andy Lutomirski <luto@amacapital.net>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Matt Mackall <mpm@selenic.com>
> Cc: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
> Cc: Marcelo Tosatti <mtosatti@redhat.com>
> Cc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
> ---
>  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
                                                                       enough,

> +there is still a scenario when we can loose soft dirty bit -- a task does
                                         lose soft dirty bits -- a task

> +unmap previously mapped memory region and then maps new one exactly at the

   unmaps a previously mapped memory region and then maps a new one at exactly the

> +same place. When unmap called the kernel internally clears PTEs values

               When unmap is called, the kernel internally clears PTE values

> +including soft dirty bit. To notify user space application about such
                        bits.

> +memory region renewal the kernel always mark new memory regions (and
                                           marks

> +expanded regions) as soft dirtified.

or:                  as soft dirty.

>  
>    This feature is actively used by the checkpoint-restore project. You
>  can find more details about it on http://criu.org
> --


-- 
~Randy

  reply	other threads:[~2013-08-20 16:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 15:31 [PATCH -mm] docs: Document soft dirty behaviour for freshly created memory regions Cyrill Gorcunov
2013-08-20 15:31 ` Cyrill Gorcunov
2013-08-20 16:57 ` Randy Dunlap [this message]
2013-08-20 16:57   ` Randy Dunlap
2013-08-20 17:01   ` Cyrill Gorcunov
2013-08-20 17:01     ` Cyrill Gorcunov
2013-08-20 17:25     ` Randy Dunlap
2013-08-20 17:25       ` Randy Dunlap
2013-08-20 18:13       ` [PATCH -mm] docs: Document soft dirty behaviour for freshly created memory regions, v3 Cyrill Gorcunov
2013-08-20 18:13         ` Cyrill Gorcunov
2013-08-20 17:06   ` [PATCH -mm] docs: Document soft dirty behaviour for freshly created memory regions, v2 Cyrill Gorcunov
2013-08-20 17:06     ` Cyrill Gorcunov
2013-08-20 21:15 ` [PATCH -mm] docs: Document soft dirty behaviour for freshly created memory regions Rob Landley
2013-08-20 21:15   ` Rob Landley
2013-08-20 21:43   ` Cyrill Gorcunov
2013-08-20 21:43     ` Cyrill Gorcunov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5213A002.7020408@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=gorcunov@gmail.com \
    --cc=kosaki.motohiro@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@amacapital.net \
    --cc=mpm@selenic.com \
    --cc=mtosatti@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=xemul@parallels.com \
    --cc=xiaoguangrong@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.