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
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
On Tue, 2013-11-05 at 13:03 -0500, Mouse wrote:
But then I read BSD's setitimer man page, and was suddenly very happy
I run something else. (Honestly, you're on the runqueue, you know
how to set timers more finely than 100Hz and you already expect to be
awake for the next 10ms, maybe do
But at least some of the BSDs run on hardware that simply cannot do
what you suggest.
Which? Genuinely curious.
The BSDs? The only one I know is Net. The hardware? The one I know
best is the KA630, the MicroVAX-II CPU (which I know rather well
because I tried to build a simulator for it).
