From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC] Simplify the Linux kernel by reducing its state space
Date: Sun, 01 Apr 2012 18:11:15 +0000 [thread overview]
Message-ID: <20120401181114.GY2450@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120401100448.GD14848@liondog.tnic>
On Sun, Apr 01, 2012 at 12:04:48PM +0200, Borislav Petkov wrote:
> On Sun, Apr 01, 2012 at 12:33:21AM +0800, Paul E. McKenney wrote:
> > Although there have been numerous complaints about the complexity of
> > parallel programming (especially over the past 5-10 years), the plain
> > truth is that the incremental complexity of parallel programming over
> > that of sequential programming is not as large as is commonly believed.
> > Despite that you might have heard, the mind-numbing complexity of modern
> > computer systems is not due so much to there being multiple CPUs, but
> > rather to there being any CPUs at all. In short, for the ultimate in
> > computer-system simplicity, the optimal choice is NR_CPUS=0.
> >
> > This commit therefore limits kernel builds to zero CPUs. This change
> > has the beneficial side effect of rendering all kernel bugs harmless.
> > Furthermore, this commit enables additional beneficial changes, for
> > example, the removal of those parts of the kernel that are not needed
> > when there are zero CPUs.
> >
> > Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
>
> Looks good, thanks for doing that.
>
> Btw, I just got confirmation from hw folk that we can actually give you
> hardware support for that code with an upcoming CPU which has NR_CPUS=0
> cores.
>
> Oh, and additionally, we can disable some of those so getting into the
> negative is also doable from the hw perspective, so feel free to explore
> that side of the problem too.
>
> ACK.
Cute! ;-)
Thanx, Paul
prev parent reply other threads:[~2012-04-01 18:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 16:33 [PATCH RFC] Simplify the Linux kernel by reducing its state space Paul E. McKenney
2012-03-31 16:40 ` Geert Uytterhoeven
2012-03-31 16:54 ` Paul E. McKenney
[not found] ` <CAHrUA35Bz68DtP-Znr=-+U+6P9CONXzN=9JdMXRfRwmVV9fy=Q@mail.gmail.com>
2012-03-31 20:14 ` Paul E. McKenney
2012-03-31 20:15 ` Linas Vepstas
2012-03-31 20:25 ` Randy Dunlap
2012-03-31 20:43 ` Paul E. McKenney
2012-03-31 21:00 ` Eric Dumazet
2012-03-31 21:21 ` Paul E. McKenney
2012-03-31 22:19 ` Lorenz Kolb
2012-03-31 22:34 ` Paul E. McKenney
2012-03-31 22:32 ` Russell King - ARM Linux
2012-04-01 1:22 ` Paul E. McKenney
2012-04-01 17:34 ` Thomas Gleixner
2012-04-01 18:12 ` Paul E. McKenney
2012-04-01 10:04 ` Borislav Petkov
2012-04-01 18:11 ` Paul E. McKenney [this message]
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=20120401181114.GY2450@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).