From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-devel@nongnu.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH qemu] sysemu: support up to 1024 vCPUs
Date: Tue, 18 Oct 2016 13:56:48 +0200 [thread overview]
Message-ID: <20161018135648.3c319b41@bahia> (raw)
In-Reply-To: <20161018130007.623f1fa8@nial.brq.redhat.com>
On Tue, 18 Oct 2016 13:00:07 +0200
Igor Mammedov <imammedo@redhat.com> wrote:
> On Tue, 11 Oct 2016 09:19:10 +1100
> Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
>
> > Ping, anyone?
> I have a similar patch
> http://patchwork.ozlabs.org/patch/681709/
> which bumps limit to 288 and does a little bit more
> so it wouldn't affect current users.
>
Heh the bumping to 1024 was kinda arbitrary but 288 would be an
improvement anyway. FYI, only Alpine class servers would benefit
from that since they have 320 threads, even if they're not officially
supported to run a KVM based hypervisor (biggest supported model is
Tuleta with 192 threads).
BTW, the afore mentioned patch keeps the current 255 limit for
pseries machine types. I guess David's answer means that the
hw/ppc/spapr.c hunk can be safely dropped.
> After that's merged, I plan to get rid of this limit and
> make that part of numa parsing code dynamic so that it
> wouldn't impose such limit/any limits on target code.
>
> >
> >
> > On 04/10/16 11:33, Alexey Kardashevskiy wrote:
> > > From: Greg Kurz <gkurz@linux.vnet.ibm.com>
> > >
> > > Some systems can already provide more than 255 hardware threads.
> > >
> > > Bumping the QEMU limit to 1024 seems reasonable:
> > > - it has no visible overhead in top;
> > > - the limit itself has no effect on hot paths.
> > >
> > > Signed-off-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
> > > Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> > > ---
> > > include/sysemu/sysemu.h | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/include/sysemu/sysemu.h b/include/sysemu/sysemu.h
> > > index ef2c50b..2ec0bd8 100644
> > > --- a/include/sysemu/sysemu.h
> > > +++ b/include/sysemu/sysemu.h
> > > @@ -173,7 +173,7 @@ extern int mem_prealloc;
> > > *
> > > * Note that cpu->get_arch_id() may be larger than MAX_CPUMASK_BITS.
> > > */
> > > -#define MAX_CPUMASK_BITS 255
> > > +#define MAX_CPUMASK_BITS 1024
> > >
> > > #define MAX_OPTION_ROMS 16
> > > typedef struct QEMUOptionRom {
> > >
> >
> >
>
next prev parent reply other threads:[~2016-10-18 11:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 0:33 [Qemu-devel] [PATCH qemu] sysemu: support up to 1024 vCPUs Alexey Kardashevskiy
2016-10-10 22:19 ` Alexey Kardashevskiy
2016-10-18 1:07 ` Alexey Kardashevskiy
2016-10-18 1:40 ` David Gibson
2016-10-18 11:00 ` Igor Mammedov
2016-10-18 11:56 ` Greg Kurz [this message]
2016-10-18 23:39 ` Alexey Kardashevskiy
2016-10-19 12:23 ` Igor Mammedov
2016-10-24 1:53 ` Alexey Kardashevskiy
2016-10-24 9:22 ` Igor Mammedov
-- strict thread matches above, loose matches on Subject: below --
2017-02-24 4:55 Alexey Kardashevskiy
2017-02-24 6:16 ` David Gibson
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=20161018135648.3c319b41@bahia \
--to=gkurz@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=imammedo@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).