Re: High scheduler wake up times

From: Shawn Bohrer
Date: Sat Jan 30 2010 - 22:57:38 EST

On Sat, Jan 30, 2010 at 04:47:16PM -0800, Arjan van de Ven wrote:
> On Sat, 30 Jan 2010 18:35:49 -0600
> Shawn Bohrer <shawn.bohrer@xxxxxxxxx> wrote:
> \
> >
> > I agree that we are currently depending on a bug in epoll. The epoll
> > implementation currently rounds up to the next jiffie, so specifying a
> > timeout of 1 ms really just wakes the process up at the next timer
> > tick. I have a patch to fix epoll by converting it to use
> > schedule_hrtimeout_range() that I'll gladly send, but I still need a
> > way to achieve the same thing.
> it's not going to help you; your expectation is incorrect.
> you CANNOT get 1000 iterations per second if you do
> <wait 1 msec>
> <do a bunch of work>
> <wait 1 msec>
> etc in a loop
> the more accurate (read: not rounding down) the implementation, the
> more not-1000 you will get, because to hit 1000 the two actions

Of course that patch makes my situation worse, which was my point. We
are depending on the _current_ epoll_wait() implementation which calls
schedule_timeout(1). You do agree that the current epoll_wait()
implementation sleeps less than 1 msec with HZ == 1000 correct? So as
long as:

work + scheduling_overhead < 1 msec

We _should_ be able to achieve 1000 iterations per second. I also
realize that with multiple worker processes I need:

(total_work + scheduling_overhead)/number_cpus < 1 msec

With the old kernel I can run 500 of these processes, and I'm hoping
that I'm simply missing the knob I need to tweak to achieve similar
performance on a recent kernel.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at