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 v2 3/4] net:bonding:Add support for IPV6 RLB to balance-alb mode
Date: Wed, 16 Mar 2022 09:57:05 +0100 [thread overview]
Message-ID: <YjGmYe9CuNiYSgk0@nanopsycho> (raw)
In-Reply-To: <c5d18455-c2ff-6e1d-c2d5-55417995c014@chinatelecom.cn>
Wed, Mar 16, 2022 at 09:45:05AM CET, sunshouxin@chinatelecom.cn wrote:
>
>在 2022/3/15 19:13, Jiri Pirko 写道:
>> Tue, Mar 15, 2022 at 08:30:07AM CET, sunshouxin@chinatelecom.cn wrote:
>> > This patch is implementing IPV6 RLB for balance-alb mode.
>> 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 previous discusion thread：
>
>https://www.spinics.net/lists/kernel/msg4187085.html
I don't see how it even remotely answers my question. Could you please
spell it out for me here again? Thanks!
next prev parent reply other threads:[~2022-03-16 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 7:30 [PATCH v2 0/4] net:bonding:Add support for IPV6 RLB to balance-alb mode Sun Shouxin
2022-03-15 7:30 ` [PATCH v2 1/4] net:ipv6:Refactor ndisc_send_na to support sending na by slave directly Sun Shouxin
2022-03-15 7:30 ` [PATCH v2 2/4] net:ipv6:Export inet6_ifa_finish_destroy and ipv6_get_ifaddr Sun Shouxin
2022-03-15 7:30 ` [PATCH v2 3/4] net:bonding:Add support for IPV6 RLB to balance-alb mode Sun Shouxin
2022-03-15 11:13 ` Jiri Pirko
2022-03-16 8:45 ` 孙守鑫
2022-03-16 8:57 ` Jiri Pirko [this message]
2022-03-15 14:37 ` kernel test robot
2022-03-15 7:30 ` [PATCH v2 4/4] net: usb:Refactor ndisc_send_na Sun Shouxin
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=YjGmYe9CuNiYSgk0@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