linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Nelson <markn@au1.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc: Track backing pages allocated by vmemmap_populate()
Date: Wed, 14 Apr 2010 09:38:46 +1000	[thread overview]
Message-ID: <201004140938.46705.markn@au1.ibm.com> (raw)
In-Reply-To: <1271157404.13059.102.camel@pasglop>

On Tuesday 13 April 2010 21:16:44 Benjamin Herrenschmidt wrote:
> On Tue, 2010-04-13 at 16:02 +1000, Mark Nelson wrote:
> > That's a good question, and one that I probably should have added to
> > the
> > commit message.
> > But, following through, it looks like we end up calling into
> > __remove_section() from mm/memory_hotplug.c and if
> > CONFIG_SPARSEMEM_VMEMMAP is enabled we just return EBUSY as freeing
> > memmap with vmemmap isn't implemented yet.
> > 
> > So for the moment, I'm not sure we have to worry about it.
> 
> We probably don't. IE. The vmemmap will remain for those struct pages,
> which means they won't need to be allocated again if some memory is
> plugged back there. If not, we just waste a bit of memory. Not a big
> deal.
> 
Excellent! That makes sense.

Thanks Ben!

Mark.

  reply	other threads:[~2010-04-13 23:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26  7:12 [PATCH] powerpc: Track backing pages used allocated by vmemmap_populate() Mark Nelson
2010-04-13  4:16 ` [PATCH v2] powerpc: Track backing pages " Mark Nelson
2010-04-13  5:24   ` Michael Ellerman
2010-04-13  6:02     ` Mark Nelson
2010-04-13 11:16       ` Benjamin Herrenschmidt
2010-04-13 23:38         ` Mark Nelson [this message]
2010-04-22  2:21           ` [PATCH v3] " Mark Nelson

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=201004140938.46705.markn@au1.ibm.com \
    --to=markn@au1.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).