public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Austin Gonyou <austin@digitalroadkill.net>
To: Matt_Domsch@Dell.com
Cc: jw@pegasys.ws, linux-kernel@vger.kernel.org
Subject: RE: [PATCH] CONFIG_NR_CPUS, redux
Date: 11 Jun 2002 23:13:17 -0500	[thread overview]
Message-ID: <1023855197.30822.7.camel@UberGeek> (raw)
In-Reply-To: <9A2D9C0E5A442340BABEBE55D81BEBDB012051FE@AUSXMPS313.aus.amer.dell.com>

For the most part, I figure that most application of Linux, ATM, is in
the server space anyway, where 2+ processors are a must.

Also, with 4 procs and HT as Matt mentioned HT below, it will *look*
like 8.(hell, might as well be at this point the way HT seems to work.)

So, the default, as it has been in the past, is for SMP to be Y. It's a
small step to turn it off, but even if you don't, *usually* it doesn't
cause UP boxes much problems.

On Tue, 2002-06-11 at 22:29, Matt_Domsch@Dell.com wrote:
> > I personally only rarely see 2-way boxes, 
> > 4-way is pretty rare, and anything more must surely count as very
> specialized.
> 
> A very large percentage of Dell PowerEdge servers sold with Red Hat Linux,
> or used with other distros, have 2 or more processors.  We today have
> servers with 1, 2, 4, or 8 CPUs, and with the advent of HyperThreading, that
> looks like even more.  More than two CPUs is not at all uncommon in the
> server space.  Desktop/notebook space, sure.
> 
> Thanks,
> Matt

-- 
Austin Gonyou <austin@digitalroadkill.net>

  reply	other threads:[~2002-06-12  4:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-12  3:29 [PATCH] CONFIG_NR_CPUS, redux Matt_Domsch
2002-06-12  4:13 ` Austin Gonyou [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-11 17:52 Robert Love
2002-06-11 18:09 ` Randy.Dunlap
2002-06-11 18:19   ` Robert Love
2002-06-11 18:21   ` Ruth Ivimey-Cook
2002-06-11 18:28     ` Robert Love
2002-06-12  1:36       ` jw schultz
2002-06-12 15:06       ` Martin J. Bligh
2002-06-12 15:22         ` William Lee Irwin III
2002-06-11 18:29     ` Martin Dalecki
2002-06-11 23:20       ` Dave Jones
2002-06-13  8:51     ` Helge Hafting
2002-06-19 11:53       ` Bill Davidsen
2002-06-11 20:10 ` Rob Radez

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=1023855197.30822.7.camel@UberGeek \
    --to=austin@digitalroadkill.net \
    --cc=Matt_Domsch@Dell.com \
    --cc=jw@pegasys.ws \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox