From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jeff Layton <jlayton@redhat.com>,
linux-nfs@vger.kernel.org, steved@redhat.com,
trond.myklebust@fys.uio.no
Subject: Re: [PATCH] mount.nfs: prefer IPv4 addresses over IPv6 (try #2)
Date: Thu, 21 Jan 2010 14:15:15 -0500 [thread overview]
Message-ID: <20100121191515.GA22021@fieldses.org> (raw)
In-Reply-To: <8E556CE2-569B-4E6D-BD02-7EF5CA84900D@oracle.com>
On Wed, Jan 20, 2010 at 10:36:36AM -0500, Chuck Lever wrote:
> For the record, we looked at Solaris behavior yesterday. With bi-family
> servers, its mount command tries IPv6 first, but appears smart enough to
> fall back to IPv4. One thing we haven't tried is to see how difficult it
> would be to fix the real problem by adding proper protocol family
> negotiation to our own mount command.
Sorry, I probably just haven't been following: what's "proper protocol
family negotiation"? I thought the only ways to negotiate were either
rpcbind (v2, v3) or trial and error (v4)?
--b.
next prev parent reply other threads:[~2010-01-21 19:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 13:27 [PATCH] mount.nfs: prefer IPv4 addresses over IPv6 (try #2) Jeff Layton
2010-01-19 15:43 ` Chuck Lever
2010-01-19 20:38 ` Jeff Layton
[not found] ` <20100119153826.67dd97a5-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-01-19 20:51 ` Trond Myklebust
2010-01-19 21:06 ` Chuck Lever
2010-01-20 13:13 ` Jeff Layton
2010-01-20 13:29 ` Jeff Layton
2010-01-20 15:36 ` Chuck Lever
2010-01-20 16:34 ` Jeff Layton
[not found] ` <20100120113422.6071bfbd-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-01-20 19:09 ` Chuck Lever
2010-01-21 19:15 ` J. Bruce Fields [this message]
2010-01-21 19:37 ` Chuck Lever
2010-01-21 19:57 ` J. Bruce Fields
2010-01-21 20:28 ` Chuck Lever
2010-01-21 21:52 ` J. Bruce Fields
2010-01-23 12:54 ` NFS/IPv6 servers on GNU/Linux? Ivan Shmakov
[not found] ` <87y6jp56cw.fsf-Hr8DDCuc/255On46OghOUKxOck334EZe@public.gmane.org>
2010-01-23 14:30 ` Jeff Layton
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=20100121191515.GA22021@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.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