On Mon, Oct 20, 2014 at 9:09 PM, Chuck Lever <chuck.lever@xxxxxxxxxx> wrote: > > > On Oct 20, 2014, at 1:33 PM, Anna Schumaker <Anna.Schumaker@xxxxxxxxxx> wrote: > > > On 10/16/14 15:40, Chuck Lever wrote: > >> So far, TCP is the only transport that supports bi-directional RPC. > >> > >> When mounting with NFSv4.1 using a transport that does not support > >> bi-directional RPC, establish a TCP sidecar connection to handle > >> backchannel traffic for a session. The sidecar transport does not > >> use its forward channel except for sending BIND_CONN_TO_SESSION > >> operations. > >> > >> This commit adds logic to create and destroy the sidecar transport. > >> Subsequent commits add logic to use the transport. > > > > I thought NFS v4.0 also uses a separate connection for the backchannel? > > For NFSv4.0, the server opens a connection to the client. For > NFSv4.1, the client opens the side car connection to the > server, and then performs BIND_CONN_TO_SESSION, an operation > not in NFSv4.0. The processes are not terribly similar. > > > Can any of that code be reused here, rather than creating new sidecar structures? > > Since it’s the client opening a connection in this case, > I don’t see any obvious common code paths that I haven’t > already re-used. I’m open to suggestions. Why aren't we doing the callbacks via RDMA as per the recommendation in RFC5667 section 5.1? -- Trond Myklebust Linux NFS client maintainer, PrimaryData trond.myklebust@xxxxxxxxxxxxxxx -- 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
