> From: Adam Jackson <a...@redhat.com> > Date: Tue, 5 Nov 2013 10:41:32 -0500 > > A default timeslice of 20ms means a pathological client can ruin up to > two frames per scheduler tick. And a fifth of a second is just insane. > > Pick two different numbers out of the hat. A 5ms slice means you can > probably keep up with two or three abusive clients, and letting it burst > to 15ms should give you about all the timeslice you need for a > fullscreen game (that's doing server-side rendering for some reason). > I suspect this is about as good as we can do without actually going > preemptive, which is an entire other nightmare.
What would the consequence of these new timings be on a kernel that has a "traditional" 10ms timeslice? I have a suspicion that the new timings would effectively disable the effects of "smart" scheduling... > --- > dix/dispatch.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) _______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
