Messages in this thread | | | Date | Fri, 17 Jun 2011 11:45:47 +0200 | From | Tejun Heo <> | Subject | Re: [PATCH] genirq: don't use flush_scheduled_work() in IRQ affinity notifiers |
| |
Hello,
On Fri, Jun 17, 2011 at 12:28:06AM +0100, Ben Hutchings wrote: > This facility is enabled on all configurations with NET && SMP && > GENERIC_HARDIRQS, but at the moment is only useful for some net drivers > (currently only one). So I don't think it should be creating a task at > boot time. Does alloc_workqueue() still create any tasks immediately?
Nope, no need to worry about it. The only added overhead is the memory occupied by workqueue itself (which includes small percpu area but one systemwide one isn't gonna hurt anyone and we've been decreasing the number of workqueues significantly). It just serves as a flush domain.
-- tejun
| |