that could very well be so - it would be helpful if you could provide
your own rough definition for the term, so that we can agree on how to
call things?
[ in any case, there's no rush here, please reply at your own pace, as
your condition allows. I wish you a speedy recovery! ]
Con, i am not 'cashing in' on anything and i'm not 'exploiting'
anything. The TASK_NONINTERACTIVE flag is totally irrelevant to my
argument because i was not testing the vanilla scheduler, i was testing
RSDL. I could have written this test using plain sockets, because i was
testing RSDL's claim of not having heuristics, i was not testing the
vanilla scheduler.
I have simply replied to this claim of yours:
and i showed you a workload under _RSDL_ that clearly shows that RSDL is
an unfair scheduler too.
my whole point was to counter the myth of 'RSDL has no heuristics'. Of
course it has heuristics, which results in unfairness. (If it didnt have
any heuristics that tilt the balance of scheduling towards sleep-intense
tasks then a default Linux desktop would not be usable at all.)
so the decision is _not_ a puristic "do we want to have heuristics or
not", the question is a more practical "which heuristics are simpler,
which heuristics are more flexible, which heuristics result in better
behavior".
Ingo
-
