On Wed, 2013-01-23 at 17:33 +0000, Alex Bligh wrote: > > --On 23 January 2013 15:34:42 +0000 "Myklebust, Trond" > <Trond.Myklebust@xxxxxxxxxx> wrote: > > > I've no idea if they do zero copy to the socket in these situations. If > > they do, then they probably have similar issues. The problem can be > > mitigated by breaking the connection on retransmission; we can't do that > > in NFS < NFSv4.1, since the duplicate replay cache is typically indexed > > to the port number (and port number reuse is difficult with TCP due to > > the existence of the TIME_WAIT state). > > If you break the connection, and the written data is now not available > to dom0 (as it's been mapped out), how would it ever get resent? IE > it's not going to be available to the RPC layer either. There are typically more than 1 outstanding RPC call at any one time. Breaking the connection would affect those other RPC calls. -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com -- 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
