From: Paul Jackson <pj@sgi.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: akpm@osdl.org, davidm@hpl.hp.com, linux-kernel@vger.kernel.org,
linux-ia64@linuxia64.org
Subject: Re: [2.6 patch] use range for NR_CPUS
Date: Thu, 8 Jan 2004 21:17:06 -0800 [thread overview]
Message-ID: <20040108211706.7772da92.pj@sgi.com> (raw)
In-Reply-To: <20040109013850.GI13867@fs.tum.de>
> The help text on ia64 didn't suggest any values. Could someone tell the
> correct values for ia64 (and if it's only a minimum value of 2)?
It keeps moving. We've announced experimental versions up to 512 CPUs,
I believe. We being SGI, and our SN product, which uses ia64 arch. So
I guess you can put that in.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-01-09 5:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 1:38 [2.6 patch] use range for NR_CPUS Adrian Bunk
2004-01-09 5:17 ` Paul Jackson [this message]
2004-01-09 23:47 ` [2.6 patch] ia64: " Adrian Bunk
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=20040108211706.7772da92.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=bunk@fs.tum.de \
--cc=davidm@hpl.hp.com \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.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.