>From: Lyle Seaman [mailto:lyleseaman@xxxxxxxxx] >Sent: Thursday, October 14, 2010 4:23 PM >To: Tayade, Nilesh >Cc: linux-nfs@xxxxxxxxxxxxxxx >Subject: Re: 'Continuation' packets in case of NFS READ. > >TCP (or UDP) handles that. It's transparent to NFS. Thanks for the information. But I also observed that if you mount multiple mount points from same server, the packets for different mount points flow through the same socket. Could you please elaborate how TCP/UDP can differentiate? Is this based on the sequence number etc.? >On Oct 14, 2010 3:50 AM, "Tayade, Nilesh" <Nilesh.Tayade@xxxxxxxxxxxx> wrote: > >>Hi, >> >>I am working on NFS packet capturing for NFS version3 protocol. In one >>of the scenarios, I tried opening a very big file and in this case the >>file data was transferred from server to client in several chunks. >> >>I observed there were some 'Continuation' RPC payload sent from server >>to client which carry file data. But even in Wireshark this doesn't >>decode any other fields apart from the file contents. >> >>Could someone please advice how client knows which particular file a >>specific 'continuation' packet belongs to? The packet doesn't even have >>the filehandle/program version data. >> >>I have attached the trace file. >> > -- Thanks, Nilesh -- 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
