Re: [PATCH 11/32] nohz/cpuset: Don't turn off the tick if rcu needsit

[Christoph Lameter]

On Thu, 22 Mar 2012, Gilad Ben-Yossef wrote:

> > Is there any way for userspace to know that the tick is not off yet due to
> > this? It would make sense for us to have busy loop in user space that
> > waits until the OS has completed all processing if that avoids future
> > latencies for the application.
> >
>
> I previously suggested having the user register to receive a signal
> when the tick
> is turned off. Since the tick is always turned off the user task is
> the current task
> by design, *I think* you can simply mark the signal pending when you
> turn the tick off.

Ok that sounds good. You would define a new signal for this?

So we would startup the application. App will do all prep work (memory
allocation, device setup etc etc) and then wait for the signal to be
received. After that it would enter the low latency processing phase.

Could we also get a signal if something disrupts the peace and switches
the timer interrupt on again?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/