[PATCH 5/7] gfs2: use workqueue instead of slow-work

2010-07-23 Thread Tejun Heo
On 07/23/2010 12:20 PM, Steven Whitehouse wrote: > Hi, > > On Tue, 2010-07-20 at 22:35 +0200, Tejun Heo wrote: >> Workqueue can now handle high concurrency. Convert gfs to use >> workqueue instead of slow-work. >> >> * Steven pointed out that recovery path might be run from allocation >> path a

[PATCH 5/7] gfs2: use workqueue instead of slow-work

2010-07-23 Thread Steven Whitehouse
Hi, On Tue, 2010-07-20 at 22:35 +0200, Tejun Heo wrote: > Workqueue can now handle high concurrency. Convert gfs to use > workqueue instead of slow-work. > > * Steven pointed out that recovery path might be run from allocation > path and thus requires forward progress guarantee without memory

Re: [PATCH 5/7] gfs2: use workqueue instead of slow-work

2010-07-23 Thread Tejun Heo
On 07/23/2010 12:20 PM, Steven Whitehouse wrote: > Hi, > > On Tue, 2010-07-20 at 22:35 +0200, Tejun Heo wrote: >> Workqueue can now handle high concurrency. Convert gfs to use >> workqueue instead of slow-work. >> >> * Steven pointed out that recovery path might be run from allocation >> path a

Re: [PATCH 5/7] gfs2: use workqueue instead of slow-work

2010-07-23 Thread Steven Whitehouse
Hi, On Tue, 2010-07-20 at 22:35 +0200, Tejun Heo wrote: > Workqueue can now handle high concurrency. Convert gfs to use > workqueue instead of slow-work. > > * Steven pointed out that recovery path might be run from allocation > path and thus requires forward progress guarantee without memory

[PATCH 5/7] gfs2: use workqueue instead of slow-work

2010-07-22 Thread Tejun Heo
On 07/20/2010 10:35 PM, Tejun Heo wrote: > Workqueue can now handle high concurrency. Convert gfs to use > workqueue instead of slow-work. > > * Steven pointed out that recovery path might be run from allocation > path and thus requires forward progress guarantee without memory > allocation.

Re: [PATCH 5/7] gfs2: use workqueue instead of slow-work

2010-07-22 Thread Tejun Heo
On 07/20/2010 10:35 PM, Tejun Heo wrote: > Workqueue can now handle high concurrency. Convert gfs to use > workqueue instead of slow-work. > > * Steven pointed out that recovery path might be run from allocation > path and thus requires forward progress guarantee without memory > allocation.

[PATCH 5/7] gfs2: use workqueue instead of slow-work

2010-07-20 Thread Tejun Heo
Workqueue can now handle high concurrency. Convert gfs to use workqueue instead of slow-work. * Steven pointed out that recovery path might be run from allocation path and thus requires forward progress guarantee without memory allocation. Create and use gfs_recovery_wq with rescuer. Please

[PATCH 5/7] gfs2: use workqueue instead of slow-work

2010-07-20 Thread Tejun Heo
Workqueue can now handle high concurrency. Convert gfs to use workqueue instead of slow-work. * Steven pointed out that recovery path might be run from allocation path and thus requires forward progress guarantee without memory allocation. Create and use gfs_recovery_wq with rescuer. Please