From: Andrew Morton <akpm@linux-foundation.org>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: 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: Track vma changes with VM_SOFTDIRTY bit
Date: Mon, 19 Aug 2013 14:08:16 -0700 [thread overview]
Message-ID: <20130819140816.6c35952c0bc19c480a9664d6@linux-foundation.org> (raw)
In-Reply-To: <20130819195836.GO23919@moon>
On Mon, 19 Aug 2013 23:58:36 +0400 Cyrill Gorcunov <gorcunov@gmail.com> wrote:
> Pavel reported that in case if vma area get unmapped and
> then mapped (or expanded) in-place, the soft dirty tracker
> won't be able to recognize this situation since it works on
> pte level and ptes are get zapped on unmap, loosing soft
> dirty bit of course.
>
> So to resolve this situation we need to track actions
> on vma level, there VM_SOFTDIRTY flag comes in. When
> new vma area created (or old expanded) we set this bit,
> and keep it here until application calls for clearing
> soft dirty bit.
>
> Thus when user space application track memory changes
> now it can detect if vma area is renewed.
Can we please update Documentation/vm/soft-dirty.txt for this?
next prev parent reply other threads:[~2013-08-19 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 19:58 [PATCH] mm: Track vma changes with VM_SOFTDIRTY bit Cyrill Gorcunov
2013-08-19 21:08 ` Andrew Morton [this message]
2013-08-19 21:10 ` 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=20130819140816.6c35952c0bc19c480a9664d6@linux-foundation.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).