Messages in this thread | | | Date | Tue, 31 Mar 2015 23:05:09 -0400 | From | Tejun Heo <> | Subject | Re: [PATCH 0/2] workqueue: fix a bug when numa mapping is changed |
| |
On Tue, Mar 31, 2015 at 11:02:42PM -0400, Tejun Heo wrote: > Ugh... so, cpu number allocation on hot-add is part of userland > interface that we're locked into? Tying hotplug and id allocation > order together usually isn't a good idea. What if the cpu up fails > while running the notifiers? The ID is already allocated and the next > cpu being brought up will be after a hole anyway. Is this even > actually gonna affect userland?
At any rate, this isn't big a deal. If the mapping has to be dynamic, it'd be great to move the mapping code from workqueue to cpu hotplug proper tho.
Thanks.
-- tejun
| |