From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
kvm-ppc@vger.kernel.org, qemu-ppc@nongnu.org,
kvm@vger.kernel.org
Cc: David Gibson <dgibson@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Bharata B Rao <bharata@linux.vnet.ibm.com>
Subject: Re: [Qemu-ppc] KVM memory slots limit on powerpc
Date: Fri, 04 Sep 2015 10:40:04 +0000 [thread overview]
Message-ID: <1441363204.2929.37.camel@au1.ibm.com> (raw)
In-Reply-To: <55E97264.6090602@redhat.com>
On Fri, 2015-09-04 at 12:28 +0200, Thomas Huth wrote:
> > Maybe some rcu protected scheme that doubles the amount of memslots
> > for
> > each overrun? Yes, that would be good and even reduce the footprint
> > for
> > systems with only a small number of memslots.
>
> Seems like Alex Williamson already posted a patchset for growable
> memslots a couple of years ago:
>
> http://www.spinics.net/lists/kvm/msg50491.html
>
> But I didn't quite spot the result in that thread why it never has
> been
> included upstream. Alex (W.), do you remember the outcome?
Isn't the memslot array *already* protected by RCU anyway ?
Cheers,
Ben.
next prev parent reply other threads:[~2015-09-04 10:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 9:35 KVM memory slots limit on powerpc Thomas Huth
2015-09-04 9:59 ` Christian Borntraeger
2015-09-04 10:04 ` [Qemu-ppc] " Alexander Graf
2015-09-04 10:07 ` Christian Borntraeger
2015-09-04 10:28 ` Thomas Huth
2015-09-04 10:40 ` Benjamin Herrenschmidt [this message]
2015-09-04 14:22 ` Alex Williamson
2015-09-04 14:45 ` Thomas Huth
2015-09-07 14:31 ` Igor Mammedov
2015-09-08 6:05 ` Thomas Huth
2015-09-08 7:11 ` Christian Borntraeger
2015-09-08 9:22 ` Thomas Huth
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=1441363204.2929.37.camel@au1.ibm.com \
--to=benh@au1.ibm.com \
--cc=agraf@suse.de \
--cc=alex.williamson@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=dgibson@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.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