I'm trying to move the callback code to asynchronous rpc calls, fix some miscellaneous problems with the callback code, and break up the nfsv4 state lock. But the callback changes aren't done yet, and are still just in my local tree; and the locking fixup is still just on paper. In the meantime, these are some smaller cleanups (and one small locking change) done in preparation; these are queued up for 2.6.30, barring any objections. Beyond this, the (vague) longer-term plan: - Make the callback rpc's asynchronous, and remove the separate kthreads. - Add a list of outstanding callbacks to the nfs4 client, for two purposes: - to allow restarting those calls after the rpc callback client is destroyed and replaced with a new one (as may happen in the setclientid case that changes the callback channel); and - to keep track of whether any callbacks are currently taking too long (which I'm provisionally defining as longer than lease_time/10 (or a second, if that's larger)). When callbacks are taking too long, we start returning cb_channel_down errors to the client's renews, and we stop handing out delegations. Having the full list of pending callbacks available may make it easier to decide when to re-enable delegations (which we should probably wait to do till *all* pending too-slow callbacks have been replied to, rather than just one of them). For locking: - Create a semaphore for each stateid, to be taken on the seqid-mutating ops. - Try to rely on spinlocks otherwise; I haven't figured out quite what's required yet. --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
