From: David Ahern <dsahern@kernel.org>
To: Sun Shouxin <sunshouxin@chinatelecom.cn>,
j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net,
davem@davemloft.net, kuba@kernel.org, yoshfuji@linux-ipv6.org,
oliver@neukum.org
Cc: 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: Thu, 17 Mar 2022 12:49:54 -0600 [thread overview]
Message-ID: <eff0021c-5a9b-5c44-3fb7-24387cf13e16@kernel.org> (raw)
In-Reply-To: <20220317061521.23985-1-sunshouxin@chinatelecom.cn>
On 3/17/22 12:15 AM, Sun Shouxin 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>
> ---
> changelog:
> v1-->v2:
> -Remove ndisc_bond_send_na and refactor ndisc_send_na.
> -In rlb_nd_xmit, if the lladdr is not local, return curr_active_slave.
> -Don't send neighbor advertisement message when receiving
> neighbor advertisement message in rlb6_update_entry_from_na.
>
> v2-->v3:
> -Don't export ndisc_send_na.
> -Use ipv6_stub->ndisc_send_na to replace ndisc_send_na
> in rlb6_update_client.
>
> v3-->v4:
> -Submit all code at a whole patch.
you misunderstood Jakub's comment. The code should evolve with small,
focused patches and each patch needs to compile and function correctly
(ie., no breakage).
You need to respond to Jiri's question about why this feature is needed.
After that:
1. patch 1 adds void *data to ndisc_send_na stub function and
ndisc_send_na direct function. Update all places that use both
ndisc_send_na to pass NULL as the data parameter.
2. patch 2 refactors ndisc_send_na to handle the new data argument
3. patch 3 exports any IPv6 functions. explain why each needs to be
exported.
4. patch 4 .... bonding changes. (bonding folks can respond on how to
introduce that change).
next prev parent reply other threads:[~2022-03-17 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 6:15 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
2022-03-17 18:49 ` David Ahern [this message]
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=eff0021c-5a9b-5c44-3fb7-24387cf13e16@kernel.org \
--to=dsahern@kernel.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--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
all inboxes | Powered by JetHome®