public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarod Wilson <jarod@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Jarod Wilson <jarod@redhat.com>
Subject: [PATCH net-next v3 0/2] bonding/balance-alb: support VMs behind bridges better
Date: Thu, 27 May 2021 16:00:49 -0400	[thread overview]
Message-ID: <20210527200051.1871092-1-jarod@redhat.com> (raw)

I've been further educated on a use case, where a bridge sits on top of
a bond, with multiple vnetX interfaces attached to virtual machines,
also acting as ports of the bridge. Each leg of the bond goes to a
different switch, but there is NO mlag/vpc in play, the bonding driver
has to handle traffic that loops back appropriately to avoid breaking
transmission. Rather than adding some sort of mac filtering to
balance-xor mode, we switched to using balance-alb, which already does
some of this, and with the tweaks provided in this series, empirically
seems to behave as desired in actual operation.

v2 attempts to support srcmac-only hashing via a modparam instead of by
adding yet another hashing mode, as well as cleaning up and clarifying
commit messages.

v3 omits two patches from the series that prove unnecessary when all
slaves get promiscuity propagated to them.

Jarod Wilson (2):
  bonding: add pure source-mac-based tx hashing option
  bonding/balance-alb: put all slaves into promisc

 Documentation/networking/bonding.rst | 13 +++++++++++++
 drivers/net/bonding/bond_main.c      | 23 +++++++++++++++--------
 2 files changed, 28 insertions(+), 8 deletions(-)

-- 
2.30.2


             reply	other threads:[~2021-05-27 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 20:00 Jarod Wilson [this message]
2021-05-27 20:00 ` [PATCH net-next v3 1/2] bonding: add pure source-mac-based tx hashing option Jarod Wilson
2021-05-28 10:10   ` Nikolay Aleksandrov
2021-05-27 20:00 ` [PATCH net-next v3 2/2] bonding/balance-alb: put all slaves into promisc Jarod Wilson

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=20210527200051.1871092-1-jarod@redhat.com \
    --to=jarod@redhat.com \
    --cc=linux-kernel@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