From: Michal Kubecek <mkubecek@suse.cz>
To: Jay Vosburgh <jay.vosburgh@canonical.com>
Cc: Jarod Wilson <jarod@redhat.com>,
linux-kernel@vger.kernel.org,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH net] bonding: show saner speed for broadcast mode
Date: Thu, 13 Aug 2020 23:36:13 +0200 [thread overview]
Message-ID: <20200813213613.qvem7gv4ri2trfvv@carpenter> (raw)
In-Reply-To: <27389.1597296596@famine>
On Wed, Aug 12, 2020 at 10:29:56PM -0700, Jay Vosburgh wrote:
> Did you notice this by inspection, or did it come up in use
> somewhere? I can't recall ever hearing of anyone using broadcast mode,
> so I'm curious if there is a use for it, but this change seems
> reasonable enough regardless.
I did actually encountered our customers using broadcast mode twice. But
I have to disappoint you, their "use for it" was rather an abuse.
One of them had a number of hosts, each having two NICs in broadcast
mode bond, one connected to one switch and one connected to another
switch (with no direct connection between the switches). Having each
packet duplicated when everything worked triggered some corner cases in
networking stack (IIRC one issue in fragment reassembly and one in TCP
lockless listener). Thankfully I was eventually able to convince them
that this kind of redundancy does not really work if one host loses
connection to one switch and another host to the other.
I don't remember the other use case from the top of my head but I'm
quite sure it made even less sense.
Michal
next prev parent reply other threads:[~2020-08-13 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 3:55 [PATCH net] bonding: show saner speed for broadcast mode Jarod Wilson
2020-08-13 5:29 ` Jay Vosburgh
2020-08-13 14:06 ` Jarod Wilson
2020-08-13 21:36 ` Michal Kubecek [this message]
2020-08-13 14:09 ` [PATCH net v2] " Jarod Wilson
2020-08-15 3:40 ` David Miller
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=20200813213613.qvem7gv4ri2trfvv@carpenter \
--to=mkubecek@suse.cz \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=jarod@redhat.com \
--cc=jay.vosburgh@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vfalico@gmail.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