From: jcm@redhat.com (Jon Masters)
To: linux-arm-kernel@lists.infradead.org
Subject: (AArch64) NR_CPUS limit
Date: Wed, 04 Feb 2015 15:23:27 -0500 [thread overview]
Message-ID: <54D27FBF.8040909@redhat.com> (raw)
Hi Folks,
We're currently patching our kernels with a (much) higher maximum for
NR_CPUS. There are some very large ARM systems coming soon - any
objections to increasing this to something like 1024 or 4096?
(If not I'll send Catalin the trivial patch)
Jon.
next reply other threads:[~2015-02-04 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 20:23 Jon Masters [this message]
2015-02-05 5:49 ` (AArch64) NR_CPUS limit Tyler Baker
2015-02-05 15:58 ` Mark Rutland
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=54D27FBF.8040909@redhat.com \
--to=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.