2012/10/22 Peter Zijlstra :
> On Sat, 2012-10-20 at 12:22 -0400, Frederic Weisbecker wrote:
>> + if (empty) {
>> + /*
>> +* If an IPI is requested, raise it right away. Otherwise
>> wait
>> +* for the next tick unless it's stopped. Now if the
2012/10/22 Peter Zijlstra pet...@infradead.org:
On Sat, 2012-10-20 at 12:22 -0400, Frederic Weisbecker wrote:
+ if (empty) {
+ /*
+* If an IPI is requested, raise it right away. Otherwise
wait
+* for the next tick unless it's stopped. Now
On Sat, 2012-10-20 at 12:22 -0400, Frederic Weisbecker wrote:
> + if (empty) {
> + /*
> +* If an IPI is requested, raise it right away. Otherwise wait
> +* for the next tick unless it's stopped. Now if the arch uses
> +* some
On Sat, 2012-10-20 at 12:22 -0400, Frederic Weisbecker wrote:
+ if (empty) {
+ /*
+* If an IPI is requested, raise it right away. Otherwise wait
+* for the next tick unless it's stopped. Now if the arch uses
+* some other
While queuing an irq work, let the caller choose between
triggering a self-IPI right away, provided the arch is able
to do so, or waiting for the next timer interrupt to run the work.
Some non-urgent enqueuers like printk may prefer not to raise
an IPI storm in case of frequent calls on short
While queuing an irq work, let the caller choose between
triggering a self-IPI right away, provided the arch is able
to do so, or waiting for the next timer interrupt to run the work.
Some non-urgent enqueuers like printk may prefer not to raise
an IPI storm in case of frequent calls on short
6 matches
Mail list logo
