From: Jiri Pirko <jiri@resnulli.us>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Nicolas Dichtel <nicolas.dichtel@6wind.com>,
Dan Geist <dan@polter.net>,
Stephen Hemminger <stephen@networkplumber.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
chenweilong@huawei.com, Jiri Pirko <jiri@mellanox.com>
Subject: Re: [Bug 194749] New: kernel bonding does not work in a network nameservice in versions above 3.10.0-229.20.1
Date: Sat, 4 Mar 2017 10:43:22 +0100 [thread overview]
Message-ID: <20170304094321.GA1753@nanopsycho> (raw)
In-Reply-To: <CAM_iQpXLS0jPAOzPe8QreXeqhPadHaOdDP5vRkW6CvLXtpReDw@mail.gmail.com>
Fri, Mar 03, 2017 at 07:11:32PM CET, xiyou.wangcong@gmail.com wrote:
>On Fri, Mar 3, 2017 at 8:03 AM, Jiri Pirko <jiri@resnulli.us> wrote:
>> If that use case exists I believe it is an abuse. Soft devices that are
>> by definition in upper-lower relationships with other devices should not
>> move to other namespaces. Prevents all kinds of issues. If you need a
>> soft device like bridge of bond within a namespace, just create it there.
>>
>
>I can't agree. Dan's use case is pretty valid, lower devices are moved
>into a netns before enslaving to the bonding device, it is perfect valid.
I'm not saying it isn't...
>NETIF_F_NETNS_LOCAL was introduced for loopback which is
>created during netns creation, forcing users to create a bond device in
>each netns is not friendly.
>
>What issues are you talking about there? Can't we just fix them?
prev parent reply other threads:[~2017-03-04 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 18:32 Fw: [Bug 194749] New: kernel bonding does not work in a network nameservice in versions above 3.10.0-229.20.1 Stephen Hemminger
2017-03-02 20:11 ` Cong Wang
2017-03-02 20:39 ` Dan Geist
2017-03-03 15:19 ` Nicolas Dichtel
2017-03-03 16:03 ` Jiri Pirko
2017-03-03 16:22 ` Dan Geist
2017-03-03 16:25 ` Nicolas Dichtel
2017-03-03 18:11 ` Cong Wang
2017-03-04 9:43 ` Jiri Pirko [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=20170304094321.GA1753@nanopsycho \
--to=jiri@resnulli.us \
--cc=chenweilong@huawei.com \
--cc=dan@polter.net \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=stephen@networkplumber.org \
--cc=xiyou.wangcong@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).