Messages in this thread | | | Date | Tue, 2 Dec 2014 14:26:55 -0500 | From | Tejun Heo <> | Subject | Re: [RFC PATCH 00/14] nfsd/sunrpc: add support for a workqueue-based nfsd |
| |
On Tue, Dec 02, 2014 at 02:18:14PM -0500, Tejun Heo wrote: ... > unbound. If strict cpu locality is likely to be beneficial and each > work item isn't likely to consume huge amount of cpu cycles, > WQ_CPU_INTENSIVE would fit better; otherwise, WQ_UNBOUND to let the > scheduler do its thing.
Hmmm... but you're already using WQ_UNBOUND. Concurrency management doesn't matter for unbound workqueues. They really just behave as shared worker thread pools. Does turning on WQ_HIGHPRI change anything? Workqueue always prefers hot workers which can lead to the hot ones being penalized for consuming too much CPU time.
Thanks.
-- tejun
| |