Re: [PATCH 2/3] work_on_cpu: Use our own workqueue.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:

> Well it turns out that I was having a less-than-usually-senile moment:
> 
> :     implement flush_work()

> Why isn't that working in this case??

how would that work in this case? We defer processing into the workqueue 
exactly because we want its per-CPU properties. We want work_on_cpu() to 
be done in the workqueue context on the CPUs that were specified, not in 
the local CPU context.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Devel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Forum]     [Linux SCSI]

  Powered by Linux