From: Nikolay Aleksandrov via Bridge <bridge@lists.linux-foundation.org>
To: netdev@vger.kernel.org
Cc: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
roopa@cumulusnetworks.com, bridge@lists.linux-foundation.org,
davem@davemloft.net
Subject: [PATCH net-next 0/2] net: bridge: add per-port unknown multicast flood control
Date: Tue, 30 Aug 2016 15:08:57 +0200 [thread overview]
Message-ID: <1472562539-23247-1-git-send-email-nikolay@cumulusnetworks.com> (raw)
Hi,
The first patch prepares the forwarding path by having the exact packet
type passed down so we can later filter based on it and the per-port
unknown mcast flood flag introduced in the second patch. It is similar to
how the per-port unknown unicast flood flag works.
Nice side-effects of patch 01 are the slight reduction of tests in the
fast-path and a few minor checkpatch fixes.
Thanks,
Nik
Nikolay Aleksandrov (2):
net: bridge: change unicast boolean to exact pkt_type
net: bridge: add per-port multicast flood flag
include/linux/if_bridge.h | 3 ++-
include/uapi/linux/if_link.h | 1 +
net/bridge/br_device.c | 8 ++++----
net/bridge/br_forward.c | 7 +++++--
net/bridge/br_if.c | 2 +-
net/bridge/br_input.c | 40 +++++++++++++++++++++++++---------------
net/bridge/br_netlink.c | 12 +++++++++---
net/bridge/br_private.h | 7 ++++++-
net/bridge/br_sysfs_if.c | 1 +
9 files changed, 54 insertions(+), 27 deletions(-)
--
2.1.4
next reply other threads:[~2016-08-30 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 13:08 Nikolay Aleksandrov via Bridge [this message]
2016-08-30 13:08 ` [PATCH net-next 1/2] net: bridge: change unicast boolean to exact pkt_type Nikolay Aleksandrov
2016-08-30 14:56 ` Stephen Hemminger
2016-08-30 14:57 ` Nikolay Aleksandrov via Bridge
2016-08-30 14:59 ` Stephen Hemminger
2016-08-30 15:00 ` Nikolay Aleksandrov
2016-08-30 15:10 ` Nikolay Aleksandrov via Bridge
2016-08-30 13:08 ` [PATCH net-next 2/2] net: bridge: add per-port multicast flood flag Nikolay Aleksandrov
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=1472562539-23247-1-git-send-email-nikolay@cumulusnetworks.com \
--to=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.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