On Saturday 25 March 2006 19:46, Radoslaw Szkodzinski wrote:
> On Saturday 25 March 2006 09:28, Con Kolivas wrote yet:
> > On Saturday 25 March 2006 19:21, Radoslaw Szkodzinski wrote:
> > > On Saturday 25 March 2006 05:01, Con Kolivas wrote yet:
> > > > I don't expect that staircase will be better in every single
> > > > situation. However it will be better more often, especially when it
> > > > counts (like audio or video skipping) and far more predictable. All
> > > > that in 300 lines less code :)
> > >
> > > I thinks the main difference is those other scheduler improvements.
> > > Some of them are compatible with staircase.
> > > Could you also try a mixed and matched 2.6.16-ck1+mm?
> >
> > You're kidding, right? Check the code.
>
> Yes and no. I was kidding about "scheduler improvements" part.
> (they're mostly NUMA-only)
>
> But of course memload, read and write latencies aren't necessarily caused
> by scheduler itself.
> (burn also reads a file)
>
> The easiest thing to do would be to add staircase to -mm and see what
> happens. It shouldn't be hard to port. (in fact, it may apply cleanly)
Yes it would be nice to believe that taking some -mm components into -ck would
actually make -ck better than everything across the board. However the policy
changes that make up staircase are not compatible with most other changes in
-mm, and most of the differences are due to the difference between the
mainline scheduler and staircase. There are some vm tweaks and the like in
-ck which only show up when you nice things though and that would improve the
results if we were comparing different nice values on interbench.
Furthermore, Mike's changes that Andre tested only worsen interbench results
so they would make staircase/ck look even better than -mm than it currently
does. Some of the things Andre found better on -mm with Mike's changes may
well be fairness related because staircase is more effective at maintaining
fairness than mainline without any special throttling.
Cheers,
Con
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
