From: Ben Greear <greearb@candelatech.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs-utils: Support binding to source address.
Date: Wed, 08 Jun 2011 12:17:55 -0700 [thread overview]
Message-ID: <4DEFCAE3.2010107@candelatech.com> (raw)
In-Reply-To: <20110608191155.GB6752@fieldses.org>
On 06/08/2011 12:11 PM, J. Bruce Fields wrote:
> On Wed, Jun 08, 2011 at 10:39:08AM -0700, greearb@candelatech.com wrote:
>> From: Ben Greear<greearb@candelatech.com>
>>
>> This lets one specify the source IP address for
>> sockets, allowing users to leverage routing rules
>> on multi-homed systems.
>>
>> Kernel patches to RPC and NFS are needed to complete
>> full functionality.
>
> Possibly dumb question: there's an ongoing effort (I think--haven't
> heard much from them recently?) to make the nfs and rpc code aware of
> which network namespace it's running in. Would that do what you need?
No, that doesn't help me. But, this effort shouldn't hurt
any namespace users, and perhaps it would even help.
> Does statd need changes too?
I don't know. With this nfs-utils patch, and my kernel
changes, I was able to direct traffic out a specific
interface across a routed network to an nfs server
and do reads/writes.
(The default route was out a different interface, so
the binding and routing rules appear to work for all
needed communication.)
As long as there is a chance of getting this in, I plan to
clean up my kernel patches, break them into smaller chunks,
and post a series for consideration.
I'm not sure that the nfs-utils changes are actually that
useful w/out the kernel changes, but at least it shouldn't
hurt anything.
Thanks,
Ben
>
> --b.
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-06-08 19:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 17:39 [PATCH] nfs-utils: Support binding to source address greearb
2011-06-08 18:36 ` Jim Rees
2011-06-08 18:39 ` Ben Greear
2011-06-08 20:45 ` Chuck Lever
2011-06-08 19:11 ` J. Bruce Fields
2011-06-08 19:17 ` Ben Greear [this message]
2011-06-08 20:41 ` Chuck Lever
2011-06-08 20:54 ` Ben Greear
2011-06-08 21:16 ` Chuck Lever
2011-06-08 21:30 ` Ben Greear
2011-06-09 5:47 ` NeilBrown
2011-06-09 6:12 ` Ben Greear
2011-06-09 6:38 ` NeilBrown
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=4DEFCAE3.2010107@candelatech.com \
--to=greearb@candelatech.com \
--cc=bfields@fieldses.org \
--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.