From: Thomas Huth <thuth@redhat.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org,
scottwood@freescale.com, Alexander Graf <agraf@suse.com>,
nikunj@linux.vnet.ibm.com
Subject: Re: [PATCH 1/1] KVM: PPC: Increase memslots to 320
Date: Wed, 09 Dec 2015 08:57:55 +0000 [thread overview]
Message-ID: <5667ED13.3080900@redhat.com> (raw)
In-Reply-To: <20151209032810.GA12287@iris.ozlabs.ibm.com>
On 09/12/15 04:28, Paul Mackerras wrote:
> On Wed, Nov 04, 2015 at 10:03:48AM +0100, Thomas Huth wrote:
>> Only using 32 memslots for KVM on powerpc is way too low, you can
>> nowadays hit this limit quite fast by adding a couple of PCI devices
>> and/or pluggable memory DIMMs to the guest.
>> x86 already increased the limit to 512 in total, to satisfy 256
>> pluggable DIMM slots, 3 private slots and 253 slots for other things
>> like PCI devices. On powerpc, we only have 32 pluggable DIMMs in
>
> I agree with increasing the limit. Is there a reason we have only 32
> pluggable DIMMs in QEMU on powerpc, not more? Should we be increasing
> that limit too? If so, maybe we should increase the number of memory
> slots to 512?
Hmmmm ... the comment before the #define in QEMU reads:
/*
* This defines the maximum number of DIMM slots we can have for sPAPR
* guest. This is not defined by sPAPR but we are defining it to 32 slots
* based on default number of slots provided by PowerPC kernel.
*/
#define SPAPR_MAX_RAM_SLOTS 32
So as far as I can see, there's indeed a possibility that we'll
increase this value once the kernel can handle more slots!
So I guess you're right and we should play save and use more slots
right from the start. I'll send a new patch with 512 instead.
>> QEMU, not 256, so we likely do not as much slots as on x86. Thus
>
> "so we likely do not need as many slots as on x86" would be better
> English.
Oops, I'm sure that was my original intention ... anyway, thanks for
pointing it out, it's always good to get some feedback as a non-native
English speaker.
Thomas
prev parent reply other threads:[~2015-12-09 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 9:03 [PATCH 0/1] KVM: PPC: Increase memslots Thomas Huth
2015-11-04 9:03 ` [PATCH 1/1] KVM: PPC: Increase memslots to 320 Thomas Huth
2015-11-18 16:19 ` Thomas Huth
2015-12-09 3:28 ` Paul Mackerras
2015-12-09 8:57 ` Thomas Huth [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=5667ED13.3080900@redhat.com \
--to=thuth@redhat.com \
--cc=agraf@suse.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=nikunj@linux.vnet.ibm.com \
--cc=paulus@ozlabs.org \
--cc=scottwood@freescale.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