From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org, David Gibson <david@gibson.dropbear.id.au>,
Eduardo Habkost <ehabkost@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RFC 0/2] numa: allocate CPUs masks dynamically
Date: Mon, 21 Nov 2016 19:46:44 +0100 [thread overview]
Message-ID: <20161121194644.6da0a005@bahia> (raw)
In-Reply-To: <e3561515-b4a2-15c8-f8ad-75408de0ae31@ozlabs.ru>
On Thu, 17 Nov 2016 17:27:20 +1100
Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
> On 17/11/16 03:02, Igor Mammedov wrote:
> > This series removes global MAX_CPUMASK_BITS constant
> > so that it won't inderectly influence maximum CPUs count
> > supported by different targets.
> >
> > It replaces statically allocated bitmasks with dynamically
> > allocated ones using '-smp maxcpus' value for setting
> > bitmasks size.
> > That would allocate just enough memory to handle all
> > CPUs indexes that a QEMU instance would ever have.
> >
> > CC: Alexey Kardashevskiy <aik@ozlabs.ru>
> > CC: Greg Kurz <gkurz@linux.vnet.ibm.com>
> > CC: David Gibson <david@gibson.dropbear.id.au>
> > CC: Eduardo Habkost <ehabkost@redhat.com>
> > CC: Paolo Bonzini <pbonzini@redhat.com>
> >
> >
> > Igor Mammedov (2):
> > add bitmap_free() wrapper
> > numa: make -numa parser dynamically allocate CPUs masks
>
> Nice, with "ulimit -n 3072", guest kernel with CONFIG_NR_CPUS=2048,
> "mc->max_cpus = 2048;" in hw/ppc/spapr.c, and "-smp 2048,threads=8" in
> QEMU cmdline, I get all 2048 CPUs in the guest.
>
Nice ! And mc->max_cpus in hw/ppc/spapr.c no longer depends on
MAX_CPUMASK_BITS since commit 079019f2e319b, so it is already
possible to bump that value (1024 ? 2048 ?).
Will you send a patch ?
>
> Tested-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>
>
> >
> > include/qemu/bitmap.h | 5 +++++
> > include/sysemu/numa.h | 2 +-
> > include/sysemu/sysemu.h | 7 -------
> > numa.c | 19 ++++++++++++-------
> > vl.c | 5 -----
> > 5 files changed, 18 insertions(+), 20 deletions(-)
> >
>
>
next prev parent reply other threads:[~2016-11-21 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 16:02 [Qemu-devel] [PATCH RFC 0/2] numa: allocate CPUs masks dynamically Igor Mammedov
2016-11-16 16:02 ` [Qemu-devel] [PATCH RFC 1/2] add bitmap_free() wrapper Igor Mammedov
2016-11-16 17:05 ` Eduardo Habkost
2016-11-16 16:02 ` [Qemu-devel] [PATCH RFC 2/2] numa: make -numa parser dynamically allocate CPUs masks Igor Mammedov
2016-11-16 17:08 ` Eduardo Habkost
2016-11-18 8:36 ` Igor Mammedov
2016-11-17 6:27 ` [Qemu-devel] [PATCH RFC 0/2] numa: allocate CPUs masks dynamically Alexey Kardashevskiy
2016-11-21 18:46 ` Greg Kurz [this message]
2016-11-22 3:05 ` Alexey Kardashevskiy
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=20161121194644.6da0a005@bahia \
--to=gkurz@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).