From: Robert Love <rml@tech9.net>
To: Barry Wu <wqb123@yahoo.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: how many cpus can linux support for SMP?
Date: 17 Jan 2002 02:51:44 -0500 [thread overview]
Message-ID: <1011253904.817.118.camel@phantasy> (raw)
In-Reply-To: <20020117065841Z288225-13996+7386@vger.kernel.org>
In-Reply-To: <20020117065841Z288225-13996+7386@vger.kernel.org>
On Thu, 2002-01-17 at 01:59, Barry Wu wrote:
> I am new to this mail list. I do not know how many CPUs linux can
> support well using SMP. If some one knows, please give me
> a reply. Thanks.
32.
"well" though may mean many things and the answer depends on your
workload.
Robert Love
next prev parent reply other threads:[~2002-01-17 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 6:59 how many cpus can linux support for SMP? Barry Wu
2002-01-17 7:36 ` Thomas Duffy
2002-01-17 7:47 ` Anton Blanchard
2002-01-17 8:29 ` Ralf Baechle
2002-01-17 7:51 ` Robert Love [this message]
2002-01-17 19:43 ` Randy.Dunlap
2002-01-19 0:30 ` James Cleverdon
2002-01-19 1:41 ` Maciej W. Rozycki
2002-01-19 21:54 ` James Cleverdon
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=1011253904.817.118.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wqb123@yahoo.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