netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: David J Wilder <wilder@us.ibm.com>
Cc: netdev@vger.kernel.org, jv@jvosburgh.net,
	pradeeps@linux.vnet.ibm.com, pradeep@us.ibm.com,
	i.maximets@ovn.org, amorenoz@redhat.com, haliu@redhat.com
Subject: Re: [PATCH net-next v1 0/2] bonding: Extend arp_ip_target format to allow for a list of vlan tags.
Date: Mon, 12 May 2025 04:20:24 +0000	[thread overview]
Message-ID: <aCF3CBlFg3G7LDGK@fedora> (raw)
In-Reply-To: <20250508183014.2554525-1-wilder@us.ibm.com>

Hi David,
On Thu, May 08, 2025 at 11:29:27AM -0700, David J Wilder wrote:
> This is a followup to this discussion:
>   https://www.spinics.net/lists/netdev/msg1085428.html
> 
> The current implementation of the arp monitor builds a list of vlan-tags by
> following the chain of net_devices above the bond. See: bond_verify_device_path().
> Unfortunately with some configurations this is not possible. One example is
> when an ovs switch is configured above the bond.
> 
> This change extends the "arp_ip_target" parameter format to allow for a list of
> vlan tags to be included for each arp target. This new list of tags is optional
> and may be omitted to preserve the current format and process of gathering tags.
> When provided the list of tags circumvents the process of gathering tags by
> using the supplied list. An empty list can be provided to simply skip the the
> process of gathering tags.
> 
> The purposed new format for arp_ip_target is:
> arp_ip_target=ipv4-address[vlan-tag\...],...
> 
> Examples:
> arp_ip_target=10.0.0.1,10.0.0.2 (Determine tags automatically for both targets)
> arp_ip_target=10.0.0.1[]        (Don't add any tags, don't gather tags)
> arp_ip_target=10.0.0.1[100/200] (Don't gather tags, use supplied list of tags)
> arp_ip_target=10.0.0.1,10.0.0.2[100] (add vlan 100 tag for 10.0.0.2.
>                                       Gather tags for 10.0.0.1.)

Thanks for the update. What about the IPv6 NS targets? Will you support it
or only the arp targets?

BTW, when add or update the parameter, please also update the bond documents
and iproute2 cmd.

Thanks
Hangbin
> 
> This is a work in process. I am requesting feedback on my approach.
> This patch allows the extended format only when setting arp_ip_target values with
> modules parameters.
> 
> TBD: Add support for sysfs, netlink and procfs.
> TBD: Kernel self tests.
> TBD: Documentation.
> 
> David J Wilder (2):
>   bonding: Adding struct arp_target
>   bonding: Extend arp_ip_target format to allow for a list of vlan tags.
> 
>  drivers/net/bonding/bond_main.c    | 163 ++++++++++++++++++++++++-----
>  drivers/net/bonding/bond_netlink.c |   4 +-
>  drivers/net/bonding/bond_options.c |  18 ++--
>  drivers/net/bonding/bond_procfs.c  |   4 +-
>  drivers/net/bonding/bond_sysfs.c   |   4 +-
>  include/net/bonding.h              |  15 ++-
>  6 files changed, 161 insertions(+), 47 deletions(-)
> 
> -- 
> 2.43.5
> 

  parent reply	other threads:[~2025-05-12  4:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08 18:29 [PATCH net-next v1 0/2] bonding: Extend arp_ip_target format to allow for a list of vlan tags David J Wilder
2025-05-08 18:29 ` [PATCH net-next v1 1/2] bonding: Adding struct arp_target David J Wilder
2025-05-10 13:16   ` Jay Vosburgh
2025-05-08 18:29 ` [PATCH net-next v1 2/2] bonding: Extend arp_ip_target format to allow for a list of vlan tags David J Wilder
2025-05-10  0:42   ` Jakub Kicinski
2025-05-10 21:06   ` kernel test robot
2025-05-12  4:20 ` Hangbin Liu [this message]
2025-05-12 23:54   ` [PATCH net-next v1 0/2] " David Wilder

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=aCF3CBlFg3G7LDGK@fedora \
    --to=liuhangbin@gmail.com \
    --cc=amorenoz@redhat.com \
    --cc=haliu@redhat.com \
    --cc=i.maximets@ovn.org \
    --cc=jv@jvosburgh.net \
    --cc=netdev@vger.kernel.org \
    --cc=pradeep@us.ibm.com \
    --cc=pradeeps@linux.vnet.ibm.com \
    --cc=wilder@us.ibm.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).