All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	netfilter-devel@vger.kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, davem@davemloft.net,
	dada1@cosmosbay.com, zbr@ioremap.net, jeff.chua.linux@gmail.com,
	paulus@samba.org, laijs@cn.fujitsu.com, jengelh@medozas.de,
	r000n@r000n.net, benh@kernel.crashing.org,
	mathieu.desnoyers@polymtl.ca
Subject: Re: [PATCH -tip 0/3] expedited "big hammer" RCU grace periods
Date: Thu, 25 Jun 2009 08:27:36 -0700	[thread overview]
Message-ID: <20090625152736.GC6761@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090625095953.GC29980@elte.hu>

On Thu, Jun 25, 2009 at 11:59:53AM +0200, Ingo Molnar wrote:
> 
> * Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> 
> > On Wed, Jun 24, 2009 at 08:03:03PM +0200, Ingo Molnar wrote:
> > > 
> > > * Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
> > > 
> > > >  include/linux/rcuclassic.h    |   15 ++-
> > > 
> > > heh, we dont have this file anymore ... as of today, right? :)
> > 
> > Ah, I was assuming that expedited RCU would happen before removal 
> > of Classic RCU.
> 
> Our general preference is to zap code.

Actually worked out nicely in this case -- the fact that Classic RCU
is no longer in -tip meant that I could dump 25% of my test cases for
expedited RCU.  ;-)

I will be posting the updated patch shortly.

> /me stares at:
> 
>   $ git diff --stat -M v2.6.30..v2.6.31-rc1 | tail -1
>   7743 files changed, 782278 insertions(+), 403162 deletions(-)
> 
> /me corrects himself:
> 
> Okay, so the zapping of code is the divine guiding principle we've 
> been following for 15 years. Ending up with a kernel that is 11 
> million lines of code is a small imperfection of mankind and is to 
> be fixed.

;-)  ;-)  ;-)

I guess that if 11 million lines of code is a small imperfection of
mankind, we can only be thankful that we are not tasked with dealing
with the large imperfections.  ;-)

							Thanx, Paul

  reply	other threads:[~2009-06-25 15:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 16:45 [PATCH -tip 0/3] expedited "big hammer" RCU grace periods Paul E. McKenney
2009-06-24 16:46 ` [PATCH -tip 1/3] synchronize_sched_expedited() primitive Paul E. McKenney
2009-06-24 16:47 ` [PATCH -tip 2/3] synchronize_sched_expedited() torture tests Paul E. McKenney
2009-06-24 16:48 ` [PATCH -tip 3/3] synchronize_sched_expedited() rcutorture doc Paul E. McKenney
2009-06-24 18:03 ` [PATCH -tip 0/3] expedited "big hammer" RCU grace periods Ingo Molnar
2009-06-24 18:44   ` Paul E. McKenney
2009-06-25  9:59     ` Ingo Molnar
2009-06-25 15:27       ` Paul E. McKenney [this message]
2009-06-25 16:47       ` Linus Torvalds
2009-06-25 17:54         ` Paul E. McKenney
  -- strict thread matches above, loose matches on Subject: below --
2009-06-25 16:07 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=20090625152736.GC6761@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=dada1@cosmosbay.com \
    --cc=davem@davemloft.net \
    --cc=jeff.chua.linux@gmail.com \
    --cc=jengelh@medozas.de \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=r000n@r000n.net \
    --cc=torvalds@linux-foundation.org \
    --cc=zbr@ioremap.net \
    /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.