From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Lorenz Kolb <linuxppcemb@lkmail.de>
Cc: linux-m32r-ja@ml.linux-m32r.org, linux-mips@linux-mips.org,
linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org,
dhowells@redhat.com, sparclinux@vger.kernel.org,
linux-s390@vger.kernel.org, linux-am33-list@redhat.com,
linux@arm.linux.org.uk, Eric Dumazet <eric.dumazet@gmail.com>,
linux-hexagon@vger.kernel.org, x86@kernel.org,
jejb@parisc-linux.org, cmetcalf@tilera.com, linux390@de.ibm.com,
tglx@linutronix.de, linux-arm-kernel@lists.infradead.org,
linux-m32r@ml.linux-m32r.org, linux-parisc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
uclinux-dist-devel@blackfin.uclinux.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH RFC] Simplify the Linux kernel by reducing its state space
Date: Sat, 31 Mar 2012 15:34:09 -0700 [thread overview]
Message-ID: <20120331223409.GM2450@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F7782ED.7050407@lkmail.de>
On Sun, Apr 01, 2012 at 12:19:25AM +0200, Lorenz Kolb wrote:
> With that patchset in mind, I am working on a really huge patch,
> which will greatly simplify the Linux kernel for the real problem
> of having that number of CPUs.
>
> That patch will have a lot of changes all over the architectures, so
> what will be the best way to post it? Should I split it architecture
> dependend and into one generic part.
>
> Currently it is a large blob of millions of changes, but will
> greatly simplify the Linux kernel.
Perhaps a branch on a public git tree? If you are doing what I suspect
you are, you will end up with a very large patch set. ;-)
Thanx, Paul
> Regards,
>
> Lorenz Kolb
>
> Am 31.03.2012 23:21, schrieb Paul E. McKenney:
> >On Sat, Mar 31, 2012 at 11:00:08PM +0200, Eric Dumazet wrote:
> >>On Sun, 2012-04-01 at 00:33 +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>
> >>>---
> >>Hmm... I believe you could go one step forward and allow negative values
> >>as well. Antimatter was proven to exist after all.
> >>
> >>Hint : nr_cpu_ids is an "int", not an "unsigned int"
> >>
> >>Bonus: Existing bugs become "must have" features.
> >;-) ;-) ;-)
> >
> >>Of course there is no hurry and this can wait 365 days.
> >James Bottomley suggested imaginary numbers of CPUs some time back,
> >and I suppose there is no reason you cannot have fractional numbers of
> >CPUs, and perhaps irrational numbers as well. Of course, these last two
> >would require use of floating-point arithmetic (or something similar)
> >in the kernel. So I guess we have at several years worth. Over to you
> >for the negative numbers. ;-)
> >
> > Thanx, Paul
> >
> >_______________________________________________
> >Linuxppc-dev mailing list
> >Linuxppc-dev@lists.ozlabs.org
> >https://lists.ozlabs.org/listinfo/linuxppc-dev
>
next prev parent reply other threads:[~2012-03-31 22:35 UTC|newest]
Thread overview: 18+ 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
2012-03-31 19:57 ` Linas Vepstas
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 [this message]
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
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=20120331223409.GM2450@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=cmetcalf@tilera.com \
--cc=dhowells@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=jejb@parisc-linux.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-am33-list@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m32r-ja@ml.linux-m32r.org \
--cc=linux-m32r@ml.linux-m32r.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=linux@arm.linux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxppcemb@lkmail.de \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=x86@kernel.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).