From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Tayade, Nilesh" <Nilesh.Tayade@netscout.com>
Cc: Lyle Seaman <lyleseaman@gmail.com>, linux-nfs@vger.kernel.org
Subject: Re: 'Continuation' packets in case of NFS READ.
Date: Thu, 14 Oct 2010 10:08:00 -0400 [thread overview]
Message-ID: <20101014140800.GC24146@fieldses.org> (raw)
In-Reply-To: <D3F292ADF945FB49B35E96C94C2061B90DAD029A@nsmail.netscout.com>
On Thu, Oct 14, 2010 at 08:30:53AM -0400, Tayade, Nilesh wrote:
> > From: Lyle Seaman [mailto:lyleseaman@gmail.com]
> > Sent: Thursday, October 14, 2010 5:35 PM
> > To: Tayade, Nilesh
> > Cc: linux-nfs@vger.kernel.org
> > Subject: Re: 'Continuation' packets in case of NFS READ.
> >
> > Sorry, that was imprecise of me. I ought to have said "it's an RPC
> function". Distinguishing between the end of one RPC and the next is
> easy with UDP. For TCP it's done with an end-of-record marker. See the
> RFCs. RFC1057 is the one I remember. Maybe there's been an update, but
> that's a good place to start.
> >
>
> Sorry, if question is not clear or I am unable to interpret your
> response and cluttering the mailing list. I shall also go through the
> RFC1057.
> What I wanted to know is -
>
> If I have file1 on mountpoint-1 and file2 on mountpoint-2. Both these
> mount points reside on same server and the respective file size is also
> big. If we look at the packets for these mount point access, we can see
> source port for packet of mount-1 same as that of packet of mount-2
> (Ofcourse, NFS port 2049 will remain same, but the other port used for
> setting up the connection also remains same).
>
> So if the 'Continuation' chunk comes, how does the client know which
> file it belongs to? The RPC packet doesn't have much info and TCP/UDP
> packets will show same ip-port pair.
If the two mountpoints are sharing the same tcp connection, then the
server will only transmit one RPC reply at a time. So "chunks" from the
two replies won't be intermingled.
--b.
next prev parent reply other threads:[~2010-10-14 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 7:48 'Continuation' packets in case of NFS READ Tayade, Nilesh
[not found] ` <AANLkTimMm0-Ux+frJq4k0PD5JyR2rMi8Bq9xXYSfjKbB@mail.gmail.com>
2010-10-14 11:26 ` Tayade, Nilesh
[not found] ` <AANLkTik0neXy5r7TZ3nr8ZT4w8T7oFG2NoySWS73GBYq@mail.gmail.com>
2010-10-14 12:30 ` Tayade, Nilesh
2010-10-14 14:08 ` J. Bruce Fields [this message]
2010-10-14 14:05 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101014140800.GC24146@fieldses.org \
--to=bfields@fieldses.org \
--cc=Nilesh.Tayade@netscout.com \
--cc=linux-nfs@vger.kernel.org \
--cc=lyleseaman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.