* Mike Galbraith <[email protected]> wrote:
> > I like your analysis, but how do you explain that these stalls
> > vanish when __update_curr is disabled?
>
> When you disable __update_curr(), you're utterly destroying the
> scheduler. There may well be a scheduler connection, but disabling
> __update_curr() doesn't tell you anything meaningful. Basically, you're
> letting all tasks run uninterrupted for just as long as they please
> (which is why busy loops lock your box solid as a rock). I'd suggest
> gathering some sched_debug stats or something... [...]
the output of the following would be nice:
http://people.redhat.com/mingo/cfs-scheduler/tools/cfs-debug-info.sh
captured while the gears are running.
Ingo
-
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]
