public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Phillips" <phillips@google.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Con Kolivas" <kernel@kolivas.org>,
	"Nick Piggin" <npiggin@suse.de>, "Mike Galbraith" <efault@gmx.de>,
	"Arjan van de Ven" <arjan@infradead.org>,
	"Peter Williams" <pwil3058@bigpond.net.au>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	caglar@pardus.org.tr, "Willy Tarreau" <w@1wt.eu>,
	"Gene Heskett" <gene.heskett@gmail.com>,
	"Mark Lord" <lkml@rtr.ca>, buddabrod <buddabrod@gmail.com>,
	"Balbir Singh" <balbir@in.ibm.com>
Subject: Re: [patch] CFS scheduler, -v9
Date: Mon, 7 May 2007 03:02:02 -0700	[thread overview]
Message-ID: <4d47a5d10705070302k3f081074k89f0122cee7ae2e@mail.gmail.com> (raw)
In-Reply-To: <20070503140911.GA21916@elte.hu>

Hi Ingo,

I just thought I would mention this, because it is certainly on my
mind.  I can't help
wondering if other folks are also concerned about this.  The thing is,
why don't you
just send your patches to Con who got this whole ball rolling and did a bunch of
great work, proving beyond any reasonable doubt that he is capable of
maintaining
this subsystem, whatever algorithm is finally adopted?  Are you worried that Con
might steal your thunder?  That somehow the scheduler is yours alone?  That you
might be perceived as less of a genius if somebody else gets credit
for their good
work?  NIH?

My perception is that you barged in to take over just when Con got things moving
after the scheduler sat and rotted for several years.  If that is in
any way accurate,
then shame on you.

Regards,

Daniel

  parent reply	other threads:[~2007-05-07 10:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 14:09 [patch] CFS scheduler, -v9 Ingo Molnar
2007-05-07  9:19 ` Nicolas Mailhot
2007-05-07 10:02 ` Daniel Phillips [this message]
2007-05-07 10:35   ` Mike Galbraith
2007-05-07 13:50   ` Mike Snitzer
2007-05-07 14:03   ` Bill Davidsen
2007-05-07 18:57     ` William Lee Irwin III
2007-05-08 10:29       ` Ingo Molnar

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=4d47a5d10705070302k3f081074k89f0122cee7ae2e@mail.gmail.com \
    --to=phillips@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=balbir@in.ibm.com \
    --cc=buddabrod@gmail.com \
    --cc=caglar@pardus.org.tr \
    --cc=efault@gmx.de \
    --cc=gene.heskett@gmail.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=mingo@elte.hu \
    --cc=npiggin@suse.de \
    --cc=pwil3058@bigpond.net.au \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=w@1wt.eu \
    /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