From: "J. Bruce Fields" <bfields@fieldses.org>
To: "William A. (Andy) Adamson" <androsadamson@gmail.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
NFS list <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4.1 callback service and UDP
Date: Fri, 17 Dec 2010 06:21:05 -0500 [thread overview]
Message-ID: <20101217112104.GC28648@fieldses.org> (raw)
In-Reply-To: <20101216172447.GA20246@fieldses.org>
On Thu, Dec 16, 2010 at 12:24:47PM -0500, J. Bruce Fields wrote:
> On Thu, Dec 16, 2010 at 11:19:50AM -0500, William A. (Andy) Adamson wrote:
> > I note that the current NFSv4.1 back channel supports UDP. Why? Should
> > we continue with UDP support?
>
> Have you tested it?
>
> Looks to me like in that case setup_callback_client() will pass
> rpc_create() a UDP svc_xprt while requesting protocol
> XPRT_TRANSPORT_BC_TCP. Looking down through the code I'm not sure
> what's going to happen. I doubt it's good....
Uh, I realize I'm talking about the NFS server (callback rpc client)
here and you were talking about the NFS client (callback rpc server)?
In any case, no, I don't think there's any reason to support a UDP
backchannel on client or server side.
It would be interesting to test the current code and see what it
actually does in this case.
--b.
>
> So, agreed, making sure we error out in the UDP case (if we don't
> already) would be a good idea.
>
> --b.
prev parent reply other threads:[~2010-12-17 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 16:19 NFSv4.1 callback service and UDP William A. (Andy) Adamson
2010-12-16 17:24 ` J. Bruce Fields
2010-12-17 11:21 ` J. Bruce Fields [this message]
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=20101217112104.GC28648@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=androsadamson@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/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.