Re: [PATCH 06/19] acpi: use queue_work_on() instead of binding workqueue worker to cpu0
From: David Howells
Date: Thu Oct 01 2009 - 09:00:57 EST
Tejun Heo <tj@xxxxxxxxxx> wrote:
> - kacpid_wq = create_singlethread_workqueue("kacpid");
> - bind_workqueue(kacpid_wq);
> - kacpi_notify_wq = create_singlethread_workqueue("kacpi_notify");
> - bind_workqueue(kacpi_notify_wq);
> - kacpi_hotplug_wq = create_singlethread_workqueue("kacpi_hotplug");
> - bind_workqueue(kacpi_hotplug_wq);
> + kacpid_wq = create_workqueue("kacpid");
> + kacpi_notify_wq = create_workqueue("kacpi_notify");
> + kacpi_hotplug_wq = create_workqueue("kacpi_hotplug");
Doesn't that then create one worker thread per CPU and then eschew all but
those attached to CPU 0? Sounds excessive, but presumably you deal with that
in later patches.
David
--
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/