fs/aio: aio_wq isn't used in memory reclaim path
authorTejun Heo <tj@kernel.org>
Wed, 26 Jan 2011 16:42:27 +0000 (17:42 +0100)
committerTejun Heo <tj@kernel.org>
Wed, 26 Jan 2011 16:42:27 +0000 (17:42 +0100)
commitd37adaa1596246929f7ab49843fd124595506175
treed7245f60b732d0753b2b2cb4851a54d5829c1838
parent1c1e8646963e319132b4cf551fbfd10b364d0aed
fs/aio: aio_wq isn't used in memory reclaim path

aio_wq isn't used during memory reclaim.  Convert to alloc_workqueue()
without WQ_MEM_RECLAIM.  It's possible to use system_wq but given that
the number of work items is determined from userland and the work item
may block, enforcing strict concurrency limit would be a good idea.

Also, move fput_work to system_wq so that aio_wq is used soley to
throttle the max concurrency of aio work items and fput_work doesn't
interact with other work items.

Signed-off-by: Tejun Heo <tj@kernel.org>
Acked-by: Jeff Moyer <jmoyer@redhat.com>
Cc: Benjamin LaHaise <bcrl@kvack.org>
Cc: linux-aio@kvack.org
fs/aio.c