From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.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:21:46 +0000 [thread overview]
Message-ID: <C7BD5B7A.CE6D%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4B97ACD30200007800033C1F@vpn.id2.novell.com>
On 10/03/2010 13:29, "Jan Beulich" <JBeulich@novell.com> wrote:
>>>> "Zhang, Xiantao" <xiantao.zhang@intel.com> 09.03.10 02:51 >>>
>> x86: Increase the default NR_CPUS to 128.
>
> While I realize my reply is a little late, I'd still like to raise the
> question
> about the tools side not coping with the new default - I would think
> that any default setting ought to imply that (within the scope of a
> project) the whole software stack should still work. At the very
> minimum CPU affinity changes (default settings on NUMA as well as
> manual ones through xm) do not presently work for CPUs beyond 64.
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?
At the end of the day packagers can make up their own minds.
-- Keir
next prev parent reply other threads:[~2010-03-10 14:21 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 [this message]
2010-03-10 14:38 ` Jan Beulich
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=C7BD5B7A.CE6D%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.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).