From: Jiri Pirko <jiri@resnulli.us>
To: 孙守鑫 <sunshouxin@chinatelecom.cn>
Cc: j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net,
davem@davemloft.net, kuba@kernel.org, yoshfuji@linux-ipv6.org,
dsahern@kernel.org, oliver@neukum.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, huyd12@chinatelecom.cn
Subject: Re: [PATCH v4] net:bonding:Add support for IPV6 RLB to balance-alb mode
Date: Mon, 21 Mar 2022 10:52:35 +0100 [thread overview]
Message-ID: <YjhK43MgpFkLFDhS@nanopsycho> (raw)
In-Reply-To: <e24c1190-ba41-6ba5-0aca-463cac2a2b2f@chinatelecom.cn>
Mon, Mar 21, 2022 at 02:17:34AM CET, sunshouxin@chinatelecom.cn wrote:
>
>在 2022/3/18 19:34, Jiri Pirko 写道:
>> Fri, Mar 18, 2022 at 10:49:02AM CET, sunshouxin@chinatelecom.cn wrote:
>> > 在 2022/3/17 16:11, Jiri Pirko 写道:
>> > > Thu, Mar 17, 2022 at 07:15:21AM CET, sunshouxin@chinatelecom.cn wrote:
>> > > > This patch is implementing IPV6 RLB for balance-alb mode.
>> > > >
>> > > > Suggested-by: Hu Yadi <huyd12@chinatelecom.cn>
>> > > > Signed-off-by: Sun Shouxin <sunshouxin@chinatelecom.cn>
>> > > Could you please reply to my question I asked for v1:
>> > > Out of curiosity, what is exactly your usecase? I'm asking because
>> > > I don't see any good reason to use RLB/ALB modes. I have to be missing
>> > > something.
>> > >
>> > > This is adding a lot of code in bonding that needs to be maintained.
>> > > However, if there is no particular need to add it, why would we?
>> > >
>> > > Could you please spell out why exactly do you need this? I'm pretty sure
>> > > that in the end well find out, that you really don't need this at all.
>> > >
>> > > Thanks!
>> >
>> > This patch is certainly aim fix one real issue in ou lab.
>> > For historical inheritance, the bond6 with ipv4 is widely used in our lab.
>> > We started to support ipv6 for all service last year, networking operation
>> > and maintenance team
>> > think it does work with ipv6 ALB capacity take it for granted due to bond6's
>> > specification
>> > but it doesn't work in the end. as you know, it is impossible to change link
>> > neworking to LACP
>> > because of huge cost and effective to online server.
>> I don't follow. Why exactly can't you use LACP? Every switch supports
>> it.
>
>
>Hi jiri
>
>
>Changing to Lacp means risk to our online service requring high available.
>
>Also,we have multiple DCs installed bond6,it is huge cost to change it.
So? This is 0 argument in this discussion. I believe that adding this
amount of code to bonding for use case that could be simply replaced by
LACP is wrong and we should not do that. The oridingal ALB/RLB
implementation was done when LACP was not that widely used. But now it
is 2022 - different story.
next prev parent reply other threads:[~2022-03-21 9:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 6:15 [PATCH v4] net:bonding:Add support for IPV6 RLB to balance-alb mode Sun Shouxin
2022-03-17 8:11 ` Jiri Pirko
2022-03-18 9:49 ` 孙守鑫
2022-03-18 11:34 ` Jiri Pirko
2022-03-21 1:17 ` 孙守鑫
2022-03-21 9:52 ` Jiri Pirko [this message]
2022-03-17 18:49 ` David Ahern
2022-03-17 20:10 ` Jay Vosburgh
2022-03-18 9:53 ` 孙守鑫
2022-03-18 9:50 ` 孙守鑫
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=YjhK43MgpFkLFDhS@nanopsycho \
--to=jiri@resnulli.us \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=huyd12@chinatelecom.cn \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=sunshouxin@chinatelecom.cn \
--cc=vfalico@gmail.com \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).