From: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
To: Pavel Emelyanov <xemul@parallels.com>
Cc: Linux MM <linux-mm@kvack.org>, Hugh Dickins <hughd@google.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH 2/3] mincore: Introduce the MINCORE_ANON bit
Date: Tue, 27 Dec 2011 17:53:58 -0500 [thread overview]
Message-ID: <CAHGf_=q3yH4RgjcTLXSxaOKU12DswnCNY9v_hWwX4h_N6WkmzA@mail.gmail.com> (raw)
In-Reply-To: <4EF8A59C.9050601@parallels.com>
> The tmpfs contents itself is supposed to be preserved, it's not a problem. The problem I'm trying
> to solve here is which page from task mappings (i.e. vm_area_struct-s) to save and which not to.
>
> Do the proposed MINCORE_RESIDENT and MINCORE_ANON bits have problems with this from
> your POV?
No problem.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-12-27 22:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-25 20:45 [RFC][PATCH 0/3] Extend the mincore() report bits Pavel Emelyanov
2011-12-25 20:45 ` [PATCH 1/3] mincore: Introduce named constant for existing bit Pavel Emelyanov
2011-12-25 20:46 ` [PATCH 2/3] mincore: Introduce the MINCORE_ANON bit Pavel Emelyanov
2011-12-26 0:05 ` KOSAKI Motohiro
2011-12-26 16:07 ` Pavel Emelyanov
2011-12-26 16:35 ` KOSAKI Motohiro
2011-12-26 16:49 ` Pavel Emelyanov
2011-12-27 22:53 ` KOSAKI Motohiro [this message]
2011-12-25 20:46 ` [PATCH 3/3] mincore: Introduce the MINCORE_SWAP bit Pavel Emelyanov
2011-12-26 8:08 ` Konstantin Khlebnikov
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='CAHGf_=q3yH4RgjcTLXSxaOKU12DswnCNY9v_hWwX4h_N6WkmzA@mail.gmail.com' \
--to=kosaki.motohiro@gmail.com \
--cc=aarcange@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=xemul@parallels.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