From: Hangbin Liu <haliu@redhat.com>
To: David Wilder <wilder@us.ibm.com>
Cc: Jay Vosburgh <jv@jvosburgh.net>,
Ilya Maximets <i.maximets@ovn.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"pradeeps@linux.vnet.ibm.com" <pradeeps@linux.vnet.ibm.com>,
Pradeep Satyanarayana <pradeep@us.ibm.com>,
Adrian Moreno Zapata <amorenoz@redhat.com>
Subject: Re: [PATCH net-next v1 1/1] bonding: Adding limmited support for ARP monitoring with ovs.
Date: Wed, 16 Apr 2025 00:35:06 +0000 [thread overview]
Message-ID: <Z_77On1togfQ1vgM@fedora> (raw)
In-Reply-To: <MW3PR15MB39138C432D2CD843C20C0C10FAB22@MW3PR15MB3913.namprd15.prod.outlook.com>
On Tue, Apr 15, 2025 at 10:13:18PM +0000, David Wilder wrote:
> >>> I agree that adding options is almost never a great solution. But I had a
> >>> similar thought. I don't think this option should be limited to OVS though,
> >>>as OVS is only one of the cases where the current verification logic is not
> >>>sufficient.
> >
> > Agreed; I wasn't really thinking about the not-OVS cases when I
> >wrote that, but whatever is changed, if anything, should be generic.
>
> >>What if we build on the arp_ip_target setting. Allow for a list of vlan tags
> >> to be appended to each target. Something like: arp_ip_target=x.x.x.x[vlan,vlan,...].
> >> If a list of tags is omitted it works as before, if a list is supplied assume we know what were doing
> >> and use that instead of calling bond_verify_device_path(). An empty list would be valid.
>
> > Hmm, that's ... not too bad; I was thinking more along the lines
> >of a "skip the checks" option, but this may be a much cleaner way to do
> >it.
>
> > That said, are you thinking that bonding would add the VLAN
> >tags, or that some third party would add them? I.e., are you trying to
> >accomodate the case wherein OVS, tc, or whatever, is adding a tag?
>
> It would be up to the administrator to add the list of tags to the arp_target list.
> I am unsure how a third party could know what tags might be added by other components.
> Knowing what tags to add to the list may be hard to figure out in a complicated configuration.
> The upside is it should be possible to configure for any list of tags even if difficult.
>
> A "skip the checks" option would be easier to code. If we skip the process of gathering tags
> would that eliminate any configurations with any vlan tags?.
+1 for "skip the checks". If arp_ip_target=x.x.x.x[vlan,vlan,...] doesn't
ask bond to add vlan tags, there is no need to set the vlan in parameter.
Since OVS, tc, netfilter can add vlan or change the output ports. A "skip
the checks" setting looks more reasonable.
Thanks
Hangbin
next prev parent reply other threads:[~2025-04-16 0:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 17:48 [PATCH net-next v1 0/1] bonding: Adding limited support for ARP monitoring with ovs David J Wilder
2025-04-11 17:48 ` [PATCH net-next v1 1/1] bonding: Adding limmited " David J Wilder
2025-04-11 23:57 ` Jay Vosburgh
2025-04-12 0:29 ` Ilya Maximets
2025-04-13 2:37 ` David Wilder
2025-04-15 20:09 ` Jay Vosburgh
2025-04-15 22:13 ` David Wilder
2025-04-16 0:35 ` Hangbin Liu [this message]
2025-04-16 1:11 ` Jay Vosburgh
2025-04-16 18:57 ` David Wilder
2025-04-18 3:59 ` Jay Vosburgh
2025-04-18 19:20 ` David Wilder
2025-04-15 13:58 ` Paolo Abeni
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=Z_77On1togfQ1vgM@fedora \
--to=haliu@redhat.com \
--cc=amorenoz@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).