Re: [ck] Re: Linus 2.6.23-rc1

Hi,

On Sat, 28 Jul 2007, Linus Torvalds wrote:

We've had people go with a splash before. Quite frankly, the current
scheduler situation looks very much like the CML2 situation. Anybody
remember that? The developer there also got rejected, the improvement was
made differently (and much more in line with existing practices and
maintainership), and life went on. Eric Raymond, however, left with a
splash.

Since I was directly involved I'd like to point out a key difference.

http://lkml.org/lkml/2002/2/21/57 was the very first start of Kconfig and
initially I didn't plan on writing a new config system. At the beginning
there was only the converter, which I did to address the issue that Eric
created a complete new and different config database, so the converter was
meant to create a more acceptable transition path. What happened next is
that I haven't got a single response from Eric, so I continued hacking on
it until was complete.

The key difference is now that Eric refused the offered help, while Con
was refused the help he needed to get his work integrated.

When Ingo posted his rewrite http://lkml.org/lkml/2007/4/13/180, Con had
already pretty much lost. I have no doubt that Ingo can quickly transform
an idea into working code and I would've been very surprised if he
wouldn't be able to turn it into something technically superior. When Ingo
figured out how to implement fair scheduling in a better way, he didn't
use this idea to help Con to improve his work. He decided instead to
work against Con and started his own rewrite, this is of course his right
to do, but then he should also accept the responsibility that Con felt his
years of work ripped apart and in vain and we have now lost a developer
who tried to address things from a different perspective.

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: [ck] Re: Linus 2.6.23-rc1
    ... actually also think that the communication between Ingo and Con ... could have been better especially when Ingo decided to write CFS ... If I tried to rewrite a kernel subsystem - should I ever happen to dig ... would inform that developer beforehand, even if it then turns out not to ...
    (Linux-Kernel)
  • Re: [ck] Re: Linus 2.6.23-rc1
    ... actually also think that the communication between Ingo and Con ... could have been better especially when Ingo decided to write CFS ... would inform that developer beforehand, even if it then turns out not to ... And aside from that there has been communication before and after this ...
    (Linux-Kernel)
  • Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS]
    ... my perception is that Ingo is simply trying to ... stated that the "problems" are in fact by design and won't be fixed. ... try to improve some areas of the kernel. ... Con worked ...
    (Linux-Kernel)
  • Scheduler Situation
    ... I am an avid reader of the LKML but I'm not a developer. ... understand basic kernel operations like memory management or CPU ... I, like many people, had been using Con's patches for years and were ... Con here. ...
    (Linux-Kernel)
  • Re: [ck] Re: Linus 2.6.23-rc1
    ... The kernel has become a community project pretty ... I tried speaking to Con and Ingo whether they could settle their issue ... and brought in good scheduler concepts and ideas to the Linux world. ...
    (Linux-Kernel)