On Fri, 21 Mar 2014 08:41:28 -0400 Jeff Layton <jlayton@xxxxxxxxxx> wrote: > That'd probably work fine too. The main point is to make sure oplock > breaks run on a different workqueue from where read or write completion > jobs run since they are operating on the lock_sem. The other jobs that > get queued to cifsiod_wq don't touch the lock_sem and shouldn't be a > problem. > OK, I'll take a look at them, and maybe I'll just move the oplock workqueue. I think you are correct and it may be best to move the one that takes the lock. Keep that one separate and that will keep the others from being blocked by it. Thanks, I'll write something up in a bit. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
