From: Laszlo Ersek <lersek@redhat.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, keir@xen.org,
stefano.stabellini@eu.citrix.com
Subject: Re: [xen-unstable bisection] complete test-amd64-i386-rhel6hvm-intel
Date: Thu, 01 Sep 2011 19:48:51 +0200 [thread overview]
Message-ID: <4E5FC583.5050306@redhat.com> (raw)
In-Reply-To: <20063.45607.355820.209628@mariner.uk.xensource.com>
On 09/01/11 18:26, Ian Jackson wrote:
>> changeset: 23802:bb9b81008733
>> user: Laszlo Ersek<lersek@redhat.com>
>> date: Wed Aug 31 15:16:14 2011 +0100
>>
>> x86: Increase the default NR_CPUS to 256
>>
>> Changeset 21012:ef845a385014 bumped the default to 128 about one and a
>> half years ago. Increase it now to 256, as systems with eg. 160
>> logical CPUs are becoming (have become) common.
>>
>> Signed-off-by: Laszlo Ersek<lersek@redhat.com>
FWIW, the hypervisor shipped in RHEL-5 has been built for 256 CPUs since April 2009, using the max_phys_cpus make macro. I posted the patch because now we changed the in-source macro definition too.
lacos
next prev parent reply other threads:[~2011-09-01 17:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 15:54 [xen-unstable bisection] complete test-amd64-i386-rhel6hvm-intel xen.org
2011-09-01 16:26 ` Ian Jackson
2011-09-01 17:22 ` Laszlo Ersek
2011-09-02 7:11 ` Ian Campbell
2011-09-01 17:48 ` Laszlo Ersek [this message]
2011-09-01 19:28 ` Andrew Jones
2011-09-02 11:08 ` Ian Jackson
-- strict thread matches above, loose matches on Subject: below --
2013-07-21 3:26 xen.org
2013-07-21 5:30 ` Ian Campbell
2013-07-21 15:15 ` Ian Campbell
2013-02-06 7:04 xen.org
2012-02-25 16:48 xen.org
2011-11-21 3:40 xen.org
2011-11-21 11:37 ` Ian Jackson
2011-11-21 11:55 ` Keir Fraser
2011-11-21 18:47 ` Keir Fraser
2011-11-21 19:43 ` Jean Guyader
2011-11-21 21:32 ` Keir Fraser
2011-11-21 21:51 ` Jean Guyader
2011-07-07 14:41 xen.org
2010-12-22 2:12 xen.org
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=4E5FC583.5050306@redhat.com \
--to=lersek@redhat.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).