From: Ben Greear <greearb@candelatech.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Support for VRF in NFS?
Date: Thu, 8 Nov 2018 08:35:26 -0800 [thread overview]
Message-ID: <90f8e9ba-3953-e2d1-56f4-421a4991cef8@candelatech.com> (raw)
In-Reply-To: <20181108153136.GA4947@fieldses.org>
On 11/08/2018 07:31 AM, J. Bruce Fields wrote:
> On Wed, Nov 07, 2018 at 09:08:16PM -0800, Ben Greear wrote:
>>
>>
>> On 11/07/2018 05:14 PM, J. Bruce Fields wrote:
>>> On Tue, Nov 06, 2018 at 01:03:54PM -0800, Ben Greear wrote:
>>>> Hello,
>>>>
>>>> I made a stab at implementing VRF support in NFS, but it appears
>>>> fairly complicated and I ended up reverting my changes....
>>>>
>>>> Is anyone working on this?
>>>>
>>>> And, if not, if anyone would like to be sponsored to work on this, please
>>>> let me know.
>>>
>>> Um, sorry--what's VRF?
>>
>> Virtual Router logic. It is sort of like network stack containers,
>> and has been solid and fully featured in the kernel since 4.16 or so.
>>
>> In the end, you effectively need to call the logic that SO_BINDTODEVICE
>> calls on the socket before binding to an IP.
>>
>> The NFS and RPC logic is a giant tangled mess to my eyes, so
>> hoping I could bribe someone else to do it :)
>
> So it's not enough to support network namespaces?
>
> What's your motivation for this?
Network namespaces are difficult to uses for lots of use cases, and thus VRF
was born.
My own motivation is that it allows me to make hundreds or thousands
of individual NFS mounts from local mac-vlan (or other virtual/physical interfaces),
for testing purposes.
Similar to my patch set that binds to local IP address, which gives similar feature
set for non-VRF configurations. These bind-local-IP patches are not upstream and were rejected in
the past as un-wanted. I'm hoping VRF support would be more acceptable.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2018-11-08 16:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 21:03 Support for VRF in NFS? Ben Greear
2018-11-08 1:14 ` J. Bruce Fields
2018-11-08 5:08 ` Ben Greear
2018-11-08 15:31 ` J. Bruce Fields
2018-11-08 16:35 ` Ben Greear [this message]
2018-11-09 9:59 ` Steven Whitehouse
2018-11-09 14:48 ` Ben Greear
[not found] ` <CAGKpdE9YMQNisieoOUbenwA8a7PhTngLTX=v8Bkznfqc2816dQ@mail.gmail.com>
2018-11-12 14:21 ` Fwd: " David Windsor
2018-11-12 14:47 ` Ben Greear
2018-11-12 16:39 ` David Windsor
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=90f8e9ba-3953-e2d1-56f4-421a4991cef8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox