Re: Scheduler policies for staircase

[Con Kolivas]

Maciej Soltysiak writes:

> Con,
>
> I have been using SCHED_BATCH on two machines now with expected
> results. So this you might consider this as another success report :-)

Great. Thanks for the report. I too use them all day every day on each 
machine I have with distributed computing clients so they're pretty well 
tested.

> Do you think that these schedulers could come into the mainline
> soon? Would you submit them to Linus without the staircase scheduler
> or would you rather wait for the whole bunch of changes to get
> rock-stable ?

It could easily be modified to suit the current scheduler. Obviously I want 
my scheduler to be considered for mainline at some stage in the future but 
there needs to be a good reason for that to occur, and the 12 other 
schedulers out there need to also be tested (we better hurry up or it could 
be twice that soon :P). At this stage I'll hold onto these patches and see 
what happens. I'd rather not have to rewrite it to suit the current 
scheduler and go through all the bugtesting again since there isn't a 
burning need for this scheduler policy in mainline at the moment. The 
lack of a large amount of feedback about staircase shows that most people 
aren't really interested in the cpu scheduler at the moment anyway.

Cheers,
Con

-
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/