On Tue, 28 Aug 2007, Al Boldi wrote:
>
> I like your analysis, but how do you explain that these stalls vanish when
> __update_curr is disabled?
It's entirely possible that what happens is that the X scheduling is just
a slightly unstable system - which effectively would turn a small
scheduling difference into a *huge* visible difference.
And the "small scheduling difference" might be as simple as "if the
process slept for a while, we give it a bit more CPU time". And then you
get into some unbalanced setup where the X scheduler makes it sleep even
more, because it fills its buffers.
Or something. I can easily see two schedulers that are trying to
*individually* be "fair", fighting it out in a way where the end result is
not very good.
I do suspect it's probably a very interesting load, so I hope Ingo looks
more at it, but I also suspect it's more than just the kernel scheduler.
Linus
-
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]
