From: Stephen Wadeley <swadeley@redhat.com>
To: netdev@vger.kernel.org
Subject: bonding.txt, broadcast mode description
Date: Wed, 04 Mar 2015 21:49:50 +0100 [thread overview]
Message-ID: <54F76FEE.1050002@redhat.com> (raw)
Dear Esteemed List Members
In my private time I work on Fedora guides and I would like to
contribute something to kernel docs and networking related man pages.
WRT doc/Documentation/networking/bonding.txt
under bonding, modes, there is currently:
broadcast or 3
Broadcast policy: transmits everything on all slave
interfaces. This mode provides fault tolerance.
How do the list members feel about changing that to:
Option 1]
Broadcast policy: All transmissions are sent on all slave interfaces.
Useful for high availability applications where duplicate packets are
sent to separate networks. Requires switch support if sending to a
single network.
Option 2]
Broadcast policy: All transmissions are sent
on all slave interfaces. Useful for high availability applications where
duplicate packets are sent to separate networks. Requires switch support
if sending to a single network. This mode might not work behind a bridge
with virtual machines without additional switch configuration.
Willing to submit patches.
Thank you
Yours sincerely
--
Stephen Wadeley
Content Author | Red Hat, Inc.
Purkynova 99 | Brno, Czech Republic
reply other threads:[~2015-03-04 20:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54F76FEE.1050002@redhat.com \
--to=swadeley@redhat.com \
--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).