From: Hangbin Liu <liuhangbin@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Jay Vosburgh <jv@jvosburgh.net>, netdev@vger.kernel.org
Subject: Re: [Question]: should we consider arp missed max during bond_ab_arp_probe()?
Date: Thu, 7 Nov 2024 01:21:31 +0000 [thread overview]
Message-ID: <ZywWG1Dov8jX7pSM@fedora> (raw)
In-Reply-To: <Zyt_58BFKnZvtsHx@nanopsycho.orion>
On Wed, Nov 06, 2024 at 03:40:39PM +0100, Jiri Pirko wrote:
> >I think they just want to make sure there is a backup for the link.
>
> Why don't they use LACP? You can have backup there as well.
Some users don't want to configure switches. Specifically, some large-scale
users don't want or don't allow to maintain the same number of switches.
Hangbin
next prev parent reply other threads:[~2024-11-07 1:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 7:39 [Question]: should we consider arp missed max during bond_ab_arp_probe()? Hangbin Liu
2024-11-06 8:34 ` Jiri Pirko
2024-11-06 9:25 ` Hangbin Liu
2024-11-06 14:40 ` Jiri Pirko
2024-11-07 1:21 ` Hangbin Liu [this message]
2024-11-07 1:21 ` Jakub Kicinski
2024-11-08 1:32 ` Jay Vosburgh
2024-11-08 2:51 ` Hangbin Liu
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=ZywWG1Dov8jX7pSM@fedora \
--to=liuhangbin@gmail.com \
--cc=jiri@resnulli.us \
--cc=jv@jvosburgh.net \
--cc=netdev@vger.kernel.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).