RE: Delete scheduler SD_WAKE_AFFINE and SD_WAKE_BALANCE flags

Chen, Kenneth W
2005-07-29T06:27:52Z

Nick Piggin wrote on Thursday, July 28, 2005 7:01 PM
> Chen, Kenneth W wrote:
> >Well, that's exactly what I'm trying to do: make them not aggressive
> >at all by not performing any load balance :-) The workload gets maximum
> >benefit with zero aggressiveness.
>
> Unfortunately we can't forget about other workloads, and we're
> trying to stay away from runtime tunables in the scheduler.

This clearly outlines an issue with the implementation. Optimize for one
type of workload has detrimental effect on another workload and vice versa.

> If we can get performance to within a couple of tenths of a percent
> of the zero balancing case, then that would be preferable I think.

I won't try to compromise between the two. If you do so, we would end up
with two half baked raw turkey. Making less aggressive load balance in the
wake up path would probably reduce performance for the type of workload you
quoted earlier and for db workload, we don't want any of them at all, not
even the code to determine whether it should be balanced or not.

Do you have an example workload you mentioned earlier that depends on
SD_WAKE_BALANCE? I would like to experiment with it so we can move this
forward instead of paper talk.

- Ken