Could you try something as simple and accepting that maybe this is a
problem?
Quite frankly, I was *planning* on merging RSDL very early after 2.6.21,
but there is one thing that has turned me completely off the whole thing:
- the people involved seem to be totally unwilling to even admit there
might be a problem.
This is like alcoholism. If you cannot admit that you might have a
problem, you'll never get anywhere. And quite frankly, the RSDL proponents
seem to be in denial ("we're always better", "it's your problem if the old
scheduler works better", "just one report of old scheduler being better").
And the thing is, if people aren't even _willing_ to admit that there may
be issues, there's *no*way*in*hell* I will merge it even for testing.
Because the whole and only point of merging RSDL was to see if it could
replace the old scheduler, and the most important feature in that case is
not whether it is perfect, BUT WHETHER ANYBODY IS INTERESTED IN TRYING TO
FIX THE INEVITABLE PROBLEMS!
See?
Can you people not see that the way you're doing that "RSDL is perfect"
chorus in the face of people who report problems, you're just making it
totally unrealistic that it will *ever* get merged.
So unless somebody steps up to the plate and actually *talks* about the
problem reports, and admits that maybe RSDL will need some tweaking, I'm
not going to merge it.
Because there is just _one_ thing that is more important than code - and
that is the willingness to fix the code...
Linus
-
