On Thu, Apr 02, 2009 at 06:06:55PM -0700, Labiaga, Ricardo wrote: > Yes, the NFS client uses a slot table for the forechannel 'struct > nfs4_slot_table' and a slot table for the backchannel. Tasks sleep on > an rpc_wait_queue if there are no available slots. Used/ unused slots > are tracked with a bit map array. When the reply is received on a slot, > the next available task is awaken. > > Yes, the callback client can certainly do the same thing. Today, the > Linux client backchannel only advertises a single slot (need to check > what Solaris does). So against Linux, having more than one slot doesn't > buy the server much right now. > > Is this something that can be addressed as an enhancement later on, or > do you need this implemented right away? I'm dropping the backchannel patches for 2.6.30, so it isn't urgent, but this is something to work on over the next month or two. I'd just like an asynchronous solution, so no big mutexes. I'm fine with the single-slot limitation if it helps, but maybe the simplest thing will be just to imitate the nfs-client code? --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
