From: Andrew Morton <akpm@zip.com.au>
To: vda@port.imtp.ilyichevsk.odessa.ua
Cc: Russ Weight <rweight@us.ibm.com>,
mingo@elte.hu, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Scalable CPU bitmasks
Date: Mon, 18 Mar 2002 23:56:07 -0800 [thread overview]
Message-ID: <3C96EF17.32C9B8A0@zip.com.au> (raw)
In-Reply-To: <20020318140700.A4635@us.ibm.com> <200203190728.g2J7Srq31344@Port.imtp.ilyichevsk.odessa.ua>
Denis Vlasenko wrote:
>
> On 18 March 2002 20:07, Russ Weight wrote:
> > While systems with more than 32 processors are still
> > out in the future, these interfaces provide a path for gradual
> > code migration. One of the primary goals is to provide current
> > functionality without affecting performance.
>
> Not so far in the future. "7.52 second kernel compile" thread is about
> timing kernel compile on the 32 CPU SMP box.
The x86 spinlock implementation underflows at 128 CPUs [1].
> I don't know whether BUG() in inlines makes them too big,
It does, on all but very recent gcc's. Strings in inlines
generally cause vast kernel bloatage.
> but _for() _loops_ in inline functions definitely do that.
> Here's one of the overgrown inlines:
Sigh. There is far too much inlining in Linux.
[1] Untested.
-
next prev parent reply other threads:[~2002-03-19 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 22:07 [PATCH] Scalable CPU bitmasks Russ Weight
2002-03-19 11:28 ` Denis Vlasenko
2002-03-19 7:56 ` Andrew Morton [this message]
2002-03-20 23:04 ` Russ Weight
-- strict thread matches above, loose matches on Subject: below --
2002-03-18 22:28 Manfred Spraul
2002-03-18 22:42 ` Tim Hockin
2002-03-18 22:44 ` Russ Weight
2002-01-30 0:32 Russ Weight
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=3C96EF17.32C9B8A0@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rweight@us.ibm.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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.