linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 26 Dec 2011 11:35:36 -0500	[thread overview]
Message-ID: <CAHGf_=rJhpQyhWiVk_BALM7SG=rgbVLscLMqdmmC4OLBR70mOA@mail.gmail.com> (raw)
In-Reply-To: <4EF89BCB.8070306@parallels.com>

2011/12/26 Pavel Emelyanov <xemul@parallels.com>:
> On 12/26/2011 04:05 AM, KOSAKI Motohiro wrote:
>>> +static unsigned char mincore_pte(struct vm_area_struct *vma, unsigned long addr, pte_t pte)
>>> +{
>>> +       struct page *pg;
>>> +
>>> +       pg = vm_normal_page(vma, addr, pte);
>>> +       if (!pg)
>>> +               return 0;
>>> +       else
>>> +               return PageAnon(pg) ? MINCORE_ANON : 0;
>>> +}
>>> +
>>
>> How do your program handle tmpfs pages (and/or ram device pages)?
>
> Do you mean mapped files from tmpfs? Currently just any other file.
> Do you see problems with this patch wrt tmpfs?

If you don't save mapped file on tmpfs or other volatile devices, the process
might not restored. The data might already destroyed. The common strategy
are two,

1) save all opened file by different ways.
2) save all mapped file even though clean file cache.

In both case, we don't reduce freezed data size. So, I'm interesting
you strategy.

--
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>

  reply	other threads:[~2011-12-26 16:35 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 [this message]
2011-12-26 16:49         ` Pavel Emelyanov
2011-12-27 22:53           ` KOSAKI Motohiro
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_=rJhpQyhWiVk_BALM7SG=rgbVLscLMqdmmC4OLBR70mOA@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