xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: [xen-unstable PATCH] x86: Increase the default NR_CPUS to 256
Date: Mon, 29 Aug 2011 12:41:59 +0200	[thread overview]
Message-ID: <4E5B6CF7.3050304@redhat.com> (raw)

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.

Thanks for considering.

Signed-off-by: Laszlo Ersek <lersek@redhat.com>

diff -r 227130622561 xen/include/asm-x86/config.h
--- a/xen/include/asm-x86/config.h	Thu Aug 25 12:03:14 2011 +0100
+++ b/xen/include/asm-x86/config.h	Mon Aug 29 12:33:20 2011 +0200
@@ -50,7 +50,7 @@
 #ifdef MAX_PHYS_CPUS
 #define NR_CPUS MAX_PHYS_CPUS
 #else
-#define NR_CPUS 128
+#define NR_CPUS 256
 #endif
 
 #ifdef __i386__

                 reply	other threads:[~2011-08-29 10:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4E5B6CF7.3050304@redhat.com \
    --to=lersek@redhat.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).