From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Xiantao Zhang <xiantao.zhang@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH]x86: Increase the default NR_CPUS to 128.
Date: Wed, 10 Mar 2010 14:38:01 +0000 [thread overview]
Message-ID: <4B97BCD90200007800033CD4@vpn.id2.novell.com> (raw)
In-Reply-To: <C7BD5B7A.CE6D%keir.fraser@eu.citrix.com>
>>> Keir Fraser <keir.fraser@eu.citrix.com> 10.03.10 15:21 >>>
>It would certainly be nice, but at least we can boot all CPUs and run VMs
>across them, minus the finer-grained control. Is this halfway default
>solution for these bigger machines worse than not making an effort at all?
Not sure - with NUMA also defaulting to on, guest creation may fail
because of the failure to enforce the affinity. Not nice, especially
since (I think; a general problem of the tools) the error indication is
rather hard to interpret by someone not knowing the source code.
>At the end of the day packagers can make up their own minds.
Certainly.
Jan
next prev parent reply other threads:[~2010-03-10 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 1:51 [PATCH]x86: Increase the default NR_CPUS to 128 Zhang, Xiantao
2010-03-10 13:29 ` Jan Beulich
2010-03-10 14:21 ` Keir Fraser
2010-03-10 14:38 ` Jan Beulich [this message]
2010-03-10 15:27 ` Keir Fraser
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=4B97BCD90200007800033CD4@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=xiantao.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).