I intend to submit the following for 2.6.31, mainly concerned with moving the nfsv4 callbacks to asynchronous rpc's. Currently we create a new kthread for each callback. But there's no real reason they need a real thread, and I'm assuming an rpc task will be lighter-weight. This should also keep the callbacks from outliving the nfsd module (though that could probably be solved some other way). Next I'd like to improve the decision about when to declare the callback channel down, and implement the callback-parameter-changing case of setclientid (and the corresponding 4.1 case). For the latter I'm currently stuck trying to decide how to do the locking necessary to prevent races between destruction of the old rpc client and lease-breaking code about to launch a new rpc task using the old rpc client. --b. -- 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
