From: Lennert Buytenhek <kernel@wantstofly.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
niv@us.ibm.com, dvhltc@us.ibm.com, dhowells@redhat.com,
lethal@linux-sh.org, matthew@wil.cx
Subject: Re: [PATCH] v3 RCU: the bloatwatch edition
Date: Fri, 3 Apr 2009 12:45:45 +0200 [thread overview]
Message-ID: <20090403104545.GI4738@xi.wantstofly.org> (raw)
In-Reply-To: <87prfukz46.fsf@basil.nowhere.org>
On Fri, Apr 03, 2009 at 08:52:41AM +0200, Andi Kleen wrote:
> >> Andrew, what do you think?
> >
> > I'm really struggling to see how the 900-odd bytes saved justifies
> > creating (yet another) variant of core kernel machinery.
>
> Also it's unclear if anything special cased !SMP is worth it for the
> future. After all multi core or SMT is becoming more and more common
> even in the embedded world.
At least for ARM, >99% of the dual core CPUs out there are non-SMP.
(With one core typically running Linux and another core typically not
running an OS at all: packet processing, DSP things, baseband stack,
etc. That second CPU core often doesn't even have an MMU.) I don't
think any SMP ARMs have been widely deployed yet.
Even if SMP ARM chips become widely available: the die area size of
a chip alone pretty much tells you the cost of that chip, and in a
world where every sub-mm^2 reduction in area matters a _lot_, I doubt
ARM CPU manufacturers will start including second CPU cores in chips
meant for things like cell phones, wireless access points and broadband
routers (ARM CPUs tend to be highly application-specific) just because
they can.
next prev parent reply other threads:[~2009-04-03 10:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 18:34 [PATCH] v2 " Paul E. McKenney
2009-03-29 20:31 ` [PATCH] v3 " Paul E. McKenney
2009-04-02 22:36 ` Ingo Molnar
2009-04-02 22:44 ` Andrew Morton
2009-04-03 0:02 ` Paul E. McKenney
2009-04-03 6:52 ` Andi Kleen
2009-04-03 10:45 ` Lennert Buytenhek [this message]
2009-04-02 22:44 ` Paul Mundt
2009-04-08 16:38 ` Ingo Molnar
2009-04-08 16:55 ` Paul Mundt
2009-04-08 18:44 ` Paul E. McKenney
2009-04-28 14:24 ` David Howells
2009-04-28 19:45 ` Paul E. McKenney
2009-04-28 21:39 ` David Howells
2009-04-29 0:57 ` Paul E. McKenney
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=20090403104545.GI4738@xi.wantstofly.org \
--to=kernel@wantstofly.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=dhowells@redhat.com \
--cc=dvhltc@us.ibm.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=paulmck@linux.vnet.ibm.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®