> > > Actually that one is various Intel people not me 8)
> >
> > Wouldn't it be better to see such things proven right in 2.5 first ?
>
> o 2.5 isnt going to be usable for that kind of thing in the near future
> o There is no code that is "new" for normal paths (in fact Marcelo
> wanted a change for the only "definitely harmless" one there was)
The sched.c change is also useless (ie. only harmful). Anton and I looked at
adapting the scheduler for hyperthreading, but it looks like the recent
changes have had the side effect of making hyperthreading + the current
scheduler "good enough". If someone wants an in-depth analysis of (1) what
is required to make the "right" decision for hyperthread scheduling with the
current scheduler (much more than the current wedge) and (2) why it doesn't
really matter anyway, please ask.
Anton, can you put the dbench graphs somewhere public?
Cheers,
Rusty.
-- Anyone who quotes me in their sig is an idiot. -- Rusty Russell. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/