mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Manfred Spraul <manfred@colorfullife.com>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [RFC, PATCH] kernel/rcu: add kfree_rcu
Date: Tue, 6 Jan 2009 14:17:55 -0800	[thread overview]
Message-ID: <20090106221755.GA19457@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090105044023.GC8080@linux.vnet.ibm.com>

On Sun, Jan 04, 2009 at 08:40:23PM -0800, Paul E. McKenney wrote:
> On Mon, Jan 05, 2009 at 10:48:11AM +0800, Lai Jiangshan wrote:
> > Paul E. McKenney wrote:
> > > 
> > > In any case, I do apologize -- since I didn't see anything from you I
> > > incorrectly assumed that you had given up on this patch.  Please accept
> > > my apologies!
> > 
> > It's my fault.
> > 
> > I'm a very low-yield developer.
> 
> Well, I am certainly not the highest-yield developer around, and I have
> probably put in at least 30,000 hours of programming over the past 35
> years, and probably half of those between 1981 and 1985.  Of course,
> a fair fraction of those hours were in languages and environments that
> are pretty much irrelevant these days.  Nevertheless, my guess is that
> you need to invest about 10,000 hours to really master programming, which
> works out to about five years at 40 hours per week of doing nothing but
> designing, coding, and debugging.
> 
> So please don't give up!

Two more things:

1.	I believe that reviewing code counts towards the 10,000 hours.
	Just in case you were curious.  ;-)

2.	To help prevent more collisions, I have posted a rough RCU
	to-do list at:

	http://www.kernel.org/pub/linux/kernel/people/paulmck/rcutodo.html.

							Thanx, Paul

  reply	other threads:[~2009-01-06 22:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02 11:25 Manfred Spraul
2009-01-02 18:55 ` Paul E. McKenney
2009-01-03 14:59   ` Manfred Spraul
2009-01-03 23:46     ` Paul E. McKenney
2009-01-04  5:50   ` Lai Jiangshan
2009-01-04 19:48     ` Paul E. McKenney
2009-01-05  2:48       ` Lai Jiangshan
2009-01-05  4:40         ` Paul E. McKenney
2009-01-06 22:17           ` Paul E. McKenney [this message]
2009-01-05  7:15       ` Manfred Spraul
2009-01-04  5:39 ` Lai Jiangshan
2009-01-04  7:07   ` Manfred Spraul
2009-01-04  8:30     ` Lai Jiangshan
2009-01-04 12:22       ` Manfred Spraul
2009-01-04 20:06         ` Paul E. McKenney
2009-01-12 17:43           ` 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=20090106221755.GA19457@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.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

Powered by JetHome