From: Hush Bensen <hush.bensen@gmail.com>
To: Pavel Emelyanov <xemul@parallels.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Cyrill Gorcunov <gorcunov@gmail.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
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>
Subject: Re: [PATCH] mm: Save soft-dirty bits on swapped pages
Date: Thu, 25 Jul 2013 16:26:44 +0800 [thread overview]
Message-ID: <51F0E144.9030304@gmail.com> (raw)
In-Reply-To: <51F0D3CA.3080902@parallels.com>
On 07/25/2013 03:29 PM, Pavel Emelyanov wrote:
> On 07/24/2013 11:40 PM, Andy Lutomirski wrote:
>> On Wed, Jul 24, 2013 at 12:04 PM, Cyrill Gorcunov <gorcunov@gmail.com> wrote:
>>> On Wed, Jul 24, 2013 at 10:55:41PM +0400, Pavel Emelyanov wrote:
>>>>> Well, some part of information already lays in pte (such as 'file' bit,
>>>>> swap entries) so it looks natural i think to work on this level. but
>>>>> letme think if use page struct for that be more convenient...
>>>> It hardly will be. Consider we have a page shared between two tasks,
>>>> then first one "touches" it and soft-dirty is put onto his PTE and,
>>>> subsequently, the page itself. The we go and clear sofr-dirty for the
>>>> 2nd task. What should we do with the soft-dirty bit on the page?
>>> Indeed, this won't help. Well then, bippidy-boppidy-boo, our
>>> pants are metaphorically on fire (c)
>> Hmm. So there are at least three kinds of memory:
>>
>> Anonymous pages: soft-dirty works
>> Shared file-backed pages: soft-dirty does not work
>> Private file-backed pages: soft-dirty works (but see below)
> The shared file-backed pages case works, but unmap-map case doesn't
What's the meaning of unmap-map case?
> preserve the soft-dirty bit. Just like the private file did. We'll
> fix this case next.
>
>> Perhaps another bit should be allocated to expose to userspace either
>> "soft-dirty", "soft-clean", or "soft-dirty unsupported"?
>>
>> There's another possible issue with private file-backed pages, though:
>> how do you distinguish clean-and-not-cowed from cowed-but-soft-clean?
>> (The former will reflect changes in the underlying file, I think, but
>> the latter won't.)
> There's a bit called PAGE_FILE bit in /proc/pagemap file introduced with
> the 052fb0d635df5d49dfc85687d94e1a87bf09378d commit.
>
> Plz, refer to Documentation/vm/pagemap.txt and soft-dirty.txt, all this
> is described there pretty well.
>
>> --Andy
> Thanks,
> Pavel
>
> --
> 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>
--
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>
next prev parent reply other threads:[~2013-07-25 8:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 16:08 Cyrill Gorcunov
2013-07-24 16:23 ` Andy Lutomirski
2013-07-24 16:37 ` Cyrill Gorcunov
2013-07-24 17:06 ` Andy Lutomirski
2013-07-24 17:17 ` Cyrill Gorcunov
2013-07-24 17:36 ` James Bottomley
2013-07-24 17:42 ` Andy Lutomirski
2013-07-24 18:15 ` Cyrill Gorcunov
2013-07-24 18:21 ` Andy Lutomirski
2013-07-24 18:52 ` Cyrill Gorcunov
2013-07-24 18:55 ` Pavel Emelyanov
2013-07-24 19:04 ` Cyrill Gorcunov
2013-07-24 19:18 ` Cyrill Gorcunov
2013-07-24 19:40 ` Andy Lutomirski
2013-07-25 7:07 ` Cyrill Gorcunov
2013-07-25 7:29 ` Pavel Emelyanov
2013-07-25 8:26 ` Hush Bensen [this message]
2013-07-25 8:43 ` Pavel Emelyanov
2013-07-25 16:02 ` Andy Lutomirski
2013-07-24 18:52 ` Pavel Emelyanov
2013-07-24 18:52 ` Pavel Emelyanov
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=51F0E144.9030304@gmail.com \
--to=hush.bensen@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--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=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