[PATCH 4/7] cifs: use workqueue instead of slow-work

On Tue, Jul 20, 2010 at 3:34 PM, Tejun Heo wrote: > Workqueue can now handle high concurrency. ?Use system_nrt_wq > instead of slow-work. > > * Updated is_valid_oplock_break() to not call cifs_oplock_break_put() > ?as advised by Steve French. ?It might cause deadlock. ?Instead, > ?reference is inc

Re: [PATCH 4/7] cifs: use workqueue instead of slow-work

On Tue, Jul 20, 2010 at 3:34 PM, Tejun Heo wrote: > Workqueue can now handle high concurrency.  Use system_nrt_wq > instead of slow-work. > > * Updated is_valid_oplock_break() to not call cifs_oplock_break_put() >  as advised by Steve French.  It might cause deadlock.  Instead, >  reference is inc

[PATCH 4/7] cifs: use workqueue instead of slow-work

Workqueue can now handle high concurrency. Use system_nrt_wq instead of slow-work. * Updated is_valid_oplock_break() to not call cifs_oplock_break_put() as advised by Steve French. It might cause deadlock. Instead, reference is increased after queueing succeeded and cifs_oplock_break() br

[PATCH 4/7] cifs: use workqueue instead of slow-work

Workqueue can now handle high concurrency. Use system_nrt_wq instead of slow-work. * Updated is_valid_oplock_break() to not call cifs_oplock_break_put() as advised by Steve French. It might cause deadlock. Instead, reference is increased after queueing succeeded and cifs_oplock_break() br