From: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
To: chucklever@gmail.com
Cc: "Trond Myklebust" <trond.myklebust@fys.uio.no>,
steved@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/2] nfs(5): Replace the term "netid" in mount option descriptions
Date: Tue, 23 Sep 2008 15:04:55 -0400 [thread overview]
Message-ID: <RTPCLUEXC1-PRDFRaqb000000d0@RTPMVEXC1-PRD.hq.netapp.com> (raw)
In-Reply-To: <76bd70e30809231011g5ed0cd11o6ccc06ab85f1a96c-JsoAwUIsXouhRSP0FMvGiw@public.gmane.org m>
At 01:11 PM 9/23/2008, Chuck Lever wrote:
>kernel's rpcbind client when it is stuck using only portmap. Plus,
>the RDMA client-side transport plays fast and loose with the xprt's
>prot field so it can get TCP for NLM traffic. I tried pulling that
>chain once before, and it's going to take some careful thought.
I have no issue fixing that, if there's a better way. The only goal
of the chain-pulling is to redirect the side protocols to UDP/TCP,
much like the "mountproto=" option does. NLM, as you mention,
is the tricky one, since it literally reaches into the NFS clnt struct
and "borrows" the transport identifier by value.
Tom.
next prev parent reply other threads:[~2008-09-23 19:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 16:16 [PATCH 0/2] nfs(5) updates Chuck Lever
[not found] ` <20080923161322.5119.20872.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-23 16:16 ` [PATCH 1/2] nfs(5): Replace the term "netid" in mount option descriptions Chuck Lever
2008-09-23 16:16 ` [PATCH 2/2] nfs(5): Clarify behavior of the mountproto= and proto= options Chuck Lever
[not found] ` <20080923161641.5119.37034.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-23 16:32 ` Talpey, Thomas
[not found] ` <RTPCLUEXC1-PRD77bie000000cb-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-09-23 16:47 ` Chuck Lever
2008-09-23 16:41 ` Talpey, Thomas
[not found] ` <RTPCLUEXC1-PRDSzbAU000000cd-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-09-23 16:55 ` Chuck Lever
2008-09-29 11:38 ` Steve Dickson
[not found] ` <20080923161636.5119.54434.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-23 16:30 ` [PATCH 1/2] nfs(5): Replace the term "netid" in mount option descriptions Talpey, Thomas
[not found] ` <RTPCLUEXC1-PRDC8wSA000000ca-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-09-23 16:46 ` Chuck Lever
2008-09-23 16:56 ` Trond Myklebust
2008-09-23 17:11 ` Chuck Lever
[not found] ` <76bd70e30809231011g5ed0cd11o6ccc06ab85f1a96c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[not found] ` <76bd70e30809231011g5ed0cd11o6ccc06ab85f1a96c-JsoAwUIsXouhRSP0FMvGiw@public.gmane.org m>
2008-09-23 19:04 ` Talpey, Thomas [this message]
[not found] ` <RTPCLUEXC1-PRDFRaqb000000d0-rtwIt2gI0FxT+ZUat5FNkAK/GNPrWCqfQQ4Iyu8u01E@public.gmane.org>
2008-09-23 19:55 ` Chuck Lever
2008-09-29 11:37 ` Steve Dickson
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=RTPCLUEXC1-PRDFRaqb000000d0@RTPMVEXC1-PRD.hq.netapp.com \
--to=thomas.talpey@netapp.com \
--cc=chucklever@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
--cc=trond.myklebust@fys.uio.no \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox