From: Christoph Lameter <clameter@sgi.com>
To: l.genoni@oltrelinux.com
Cc: Daniel J Blueman <daniel.blueman@gmail.com>,
Rajib Majumder <rajibm2005@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
l.genoni@sns.it
Subject: Re: Kernel Scalability
Date: Fri, 4 May 2007 09:45:49 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705040943540.22097@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0705021933320.14034@Phoenix.oltrelinux.com>
On Wed, 2 May 2007, l.genoni@oltrelinux.com wrote:
> To stay on systems probably more familiar to the user who asked this question,
> there are also some 64 core X86_64 bot AMD and Intel out there, here the 2.6
> kernel is doing very well even on those intel CPU with shared L2 cache.
> I have some 16 and 32 core Opteron and never had scalability problems.
> You have to pay a lot of attention to your kernel configuration (100 HZ, just
> BKL preemption), and to the filesystems you decide to use.
It becomes a hardware issue at higher cpu counts. Commodity hardware is
not designed to handle these high processor counts thus workarounds like
listed above become necessary. Our 512 processor systems have been running
with 1024 HZ for a long time. Plus you really need a good filesystem
(XFS).
next prev parent reply other threads:[~2007-05-04 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 15:43 Daniel J Blueman
2007-05-02 16:54 ` Tony Luck
2007-05-02 17:39 ` l.genoni
2007-05-02 18:06 ` William Lee Irwin III
2007-05-04 16:45 ` Christoph Lameter [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-02 12:56 Rajib Majumder
2007-05-02 16:54 ` Kevin Fox
2007-05-04 16:43 ` Christoph Lameter
2007-05-02 17:55 ` Eric W. Biederman
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=Pine.LNX.4.64.0705040943540.22097@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=daniel.blueman@gmail.com \
--cc=l.genoni@oltrelinux.com \
--cc=l.genoni@sns.it \
--cc=linux-kernel@vger.kernel.org \
--cc=rajibm2005@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
all inboxes | Powered by JetHome®