[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0709141630320.1817@scrub.home>
Date: Fri, 14 Sep 2007 16:50:22 +0200 (CEST)
From: Roman Zippel <zippel@...ux-m68k.org>
To: Arjan van de Ven <arjan@...radead.org>
cc: Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Mike Galbraith <efault@....de>
Subject: Re: [announce] CFS-devel, performance improvements
Hi,
On Fri, 14 Sep 2007, Arjan van de Ven wrote:
> > This is ridiculous, I asked you multiple times to explain to me some
> > of the differences relative to CFS as response to the splitup
> > requests. Not once did you react, you didn't even ask what I'd like
> > to know specifically.
>
> Roman,
>
> this is... a strange comment. It almost sounds like you were holding
> the splitup hostage depending on some other thing happening.... that's
> not a good attitude in my book. Having big-blob patches that do many
> things at the same time leads to them being impossible to apply. Linux
> works by having smaller incrementals. You know that; you've been around
> for a long time.
There is actually a very simple reason for that, the actual patch is not
my primary focus, for me it's actually more an afterthought of the actual
design to show that it actually works.
My primary interest is a _discussion_ of the scheduler design, but Ingo
insists on patches. Sorry, but I don't really work this way, I want to
think things through _first_, I need a solid concept and I don't like to
rely on guesswork.
How much response would I have gotten if I had only posted the example
program and the math description as I initially planned?
bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists