From: Willy Tarreau <w@1wt.eu>
To: Rene Herman <rene.herman@gmail.com>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Are we properly prepared to handle 3 Socket setups?
Date: Sun, 12 Aug 2007 10:41:12 +0200 [thread overview]
Message-ID: <20070812084112.GL6002@1wt.eu> (raw)
In-Reply-To: <46BE621E.9090509@gmail.com>
On Sun, Aug 12, 2007 at 03:27:58AM +0200, Rene Herman wrote:
> On 08/12/2007 03:08 AM, Jesper Juhl wrote:
>
> >This may be a little off topic, but I think it's interresting enough
> >to warrent a single mail.
> >
> >I just saw a news article (http://www.theinquirer.net/?article=41610)
> >about a 3 Socket Opteron motherboard and couldn't help but wonder if
> >we are prepared to deal with such a beast, so I thought I'd inform
> >everyone :-)
> >
> >I'm guessing equipping such a board with 3 single core CPU's could
> >show up some interresting corner cases in schedular code and
> >elsewhere, I'll bet we have some assumptions somewhere about
> >nr_of_cpus being an even number...
>
> I would hope the N=1 case will have flushed out enough of those... :-|
Well, 1 could be seen as even number in base 2, it's 2^0 and has only
one bit set.
Willy
next prev parent reply other threads:[~2007-08-12 8:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 1:08 Are we properly prepared to handle 3 Socket setups? Jesper Juhl
2007-08-12 1:27 ` Rene Herman
2007-08-12 1:52 ` Jesper Juhl
2007-08-12 3:17 ` Rene Herman
2007-08-12 3:29 ` Roland Dreier
2007-08-12 3:36 ` Rene Herman
2007-08-12 8:35 ` Andrew Morton
2007-08-12 20:00 ` Rene Herman
2007-08-13 20:44 ` Christoph Lameter
2007-08-12 7:24 ` Paul Mundt
2007-08-12 8:41 ` Willy Tarreau [this message]
2007-08-12 11:46 ` Andi Kleen
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=20070812084112.GL6002@1wt.eu \
--to=w@1wt.eu \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@gmail.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