On Jan 27, 2014, at 12:25, andros@xxxxxxxxxx wrote: > From: Andy Adamson <andros@xxxxxxxxxx> > > Pre-allocating session slots for RPC tasks waking up from a wait queue provides > a shorter slot allocation code path and can help performance. > > Durring multiple server reboots (interface moves), the pre-allocated > slot can be held and not freed as a task is transferred to various slot table > wait queues and the state manager is draining these queues. Not freeing the > slots results in a state manager hang waiting for completion on the slot > table draining. In this case, performance is not a consideration as the > client is in recovery of a session or a clientid. > I’m not understanding this reasoning. If the slot table is drained, then the slots must be returned to the session manager by all outstanding RPC calls so that the state manager thread can go about its business. By what mechanism are these slots being held and not freed here? > Prevent this state manager hang by not pre-allocating session slots, but > just wake up the tasks and let them grab a sessions slot in the > nfs4_alloc_slot call in nfs41-setup_sequence. If the slots are already held, then how does this help? -- Trond Myklebust Linux NFS client maintainer -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
