All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
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 21:01:05 +0400	[thread overview]
Message-ID: <20130820170105.GM18673@moon> (raw)
In-Reply-To: <5213A002.7020408@infradead.org>

On Tue, Aug 20, 2013 at 09:57:38AM -0700, Randy Dunlap wrote:
> >  
> > +  While in most cases tracking memory changes by #PF-s is more than enough
>                                                                        enough,

?

For the rest -- thanks a LOT Randy, I'll update.

--
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: Cyrill Gorcunov <gorcunov@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
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 21:01:05 +0400	[thread overview]
Message-ID: <20130820170105.GM18673@moon> (raw)
In-Reply-To: <5213A002.7020408@infradead.org>

On Tue, Aug 20, 2013 at 09:57:38AM -0700, Randy Dunlap wrote:
> >  
> > +  While in most cases tracking memory changes by #PF-s is more than enough
>                                                                        enough,

?

For the rest -- thanks a LOT Randy, I'll update.

  reply	other threads:[~2013-08-20 17:01 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
2013-08-20 16:57   ` Randy Dunlap
2013-08-20 17:01   ` Cyrill Gorcunov [this message]
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=20130820170105.GM18673@moon \
    --to=gorcunov@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.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=rdunlap@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.