Messages in this thread | | | Subject | Re: [PATCH 39/40] gfs2: use workqueue instead of slow-work | From | Steven Whitehouse <> | Date | Mon, 18 Jan 2010 09:45:59 +0000 |
| |
Hi,
On Mon, 2010-01-18 at 09:57 +0900, Tejun Heo wrote: > Workqueue can now handle high concurrency. Use system_long_wq instead > of slow-work. > > Signed-off-by: Tejun Heo <tj@kernel.org> > Cc: Steven Whitehouse <swhiteho@redhat.com>
Acked-by: Steven Whitehouse <swhiteho@redhat.com> on two conditions:
i) That scheduling work on this new workqueue will not require any GFP_KERNEL allocations (even hidden ones such as starting new threads) before the work runs. This is required since the recovery code must not call into the fs until after its recovered. ii) That there is no interaction between this workqueue and the "delayed" workqueue which the glock code uses since the recovery must not block that workqueue, nor must that workqueue block recovery.
Having read briefly through the other patches, I believe that both those two conditions are met, but I thought I'd ask too, just to be on the safe side. Otherwise it looks like a nice clean up,
Steve.
| |