linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@ozlabs.org>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
	bharata@linux.vnet.ibm.com, arbab@linux.vnet.ibm.com,
	npiggin@gmail.com, mikey@neuling.org, cyrilbur@gmail.com,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/powernv: Increase memory block size to 1GB on radix
Date: Thu, 7 Sep 2017 15:17:41 +1000	[thread overview]
Message-ID: <20170907151741.41ee33a8@kryten> (raw)
In-Reply-To: <ab33351f-1d52-2e55-8aeb-32813ca52e94@linux.vnet.ibm.com>

Hi,

> There is a similar issue being worked on w.r.t pseries.
> 
> https://lkml.kernel.org/r/1502357028-27465-1-git-send-email-bharata@linux.vnet.ibm.com
> 
> The question is should we map these regions ? ie, we need to tell the 
> kernel memory region that we would like to hot unplug later so that
> we avoid doing kernel allocations from that. If we do that, then we
> can possibly map them via 2M size ?

But all of memory on PowerNV should be able to be hot unplugged, so
there are two options as I see it - either increase the memory block
size, or map everything with 2MB pages. 

Anton

  reply	other threads:[~2017-09-07  5:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07  5:05 [PATCH] powerpc/powernv: Increase memory block size to 1GB on radix Anton Blanchard
2017-09-07  5:09 ` Aneesh Kumar K.V
2017-09-07  5:17   ` Anton Blanchard [this message]
2017-09-07  7:21     ` Benjamin Herrenschmidt
2017-09-08 21:51       ` Balbir Singh
2017-09-07 15:59     ` Reza Arbab
2017-09-08  1:15       ` Anton Blanchard
2017-09-09 21:30         ` Michael Ellerman
2017-10-06 11:10 ` Michael Ellerman

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=20170907151741.41ee33a8@kryten \
    --to=anton@ozlabs.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=arbab@linux.vnet.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=bharata@linux.vnet.ibm.com \
    --cc=cyrilbur@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=paulus@samba.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).