Linux Container Development
 help / color / mirror / Atom feed
From: Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 1/1] checkpoint: Note checkpointability of mm_struct (v2)
Date: Wed, 04 Mar 2009 14:44:46 -0800	[thread overview]
Message-ID: <1236206687.22399.44.camel@nimitz> (raw)
In-Reply-To: <20090304223505.GA27248-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>

On Wed, 2009-03-04 at 16:35 -0600, Serge E. Hallyn wrote:
> I was especially curious whether using vm_stat_account to catch the
> offending mmaps seemed sensible.

I'm leery about it, but semi-ok since it seems like a common enough
place.  

Can you check that it works on with hugetlbfs?  Some of those paths can
get kinda screwy.  I don't know how you picked vm_stat_account(), but as
long as it is paired closely with the allocations of the vma structs
themselves you should be OK.

Please do send to linux-mm when ready, though.

-- Dave

      parent reply	other threads:[~2009-03-04 22:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 16:11 [PATCH 1/1] checkpoint: Note checkpointability of mm_struct (v2) Serge E. Hallyn
2009-03-04 22:01 ` Dan Smith
     [not found]   ` <87iqmpvtfw.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2009-03-04 22:35     ` Serge E. Hallyn
     [not found]       ` <20090304223505.GA27248-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-03-04 22:44         ` Dave Hansen [this message]

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=1236206687.22399.44.camel@nimitz \
    --to=dave-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    /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