From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: netdev@vger.kernel.org
Cc: idosch@mellanox.com, jiri@resnulli.us,
stephen@networkplumber.org, bridge@lists.linux-foundation.org,
roopa@cumulusnetworks.com, davem@davemloft.net,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Subject: [PATCH net-next 0/2] net: bridge: allow user-space to add ext learned entries
Date: Thu, 23 Mar 2017 12:27:11 +0200 [thread overview]
Message-ID: <1490264833-28867-1-git-send-email-nikolay@cumulusnetworks.com> (raw)
Hi,
This set adds the ability to add externally learned entries from
user-space. For symmetry and proper function we need to allow SW entries
to take over HW learned ones (similar to how HW can take over SW entries
currently) which is needed for our use case (evpn) where we have pure SW
ports and HW ports mixed in a single bridge. This does not play well with
switchdev devices currently because there's no feedback when the entry is
taken over, but this case has never worked anyway and feedback can be
easily added when needed.
Patch 02 simply allows to use NTF_EXT_LEARNED from user-space, we already
have Quagga patches that make use of this functionality.
Thanks,
Nik
Nikolay Aleksandrov (2):
net: bridge: allow SW learn to take over HW fdb entries
net: bridge: allow to add externally learned entries from user-space
net/bridge/br_fdb.c | 5 +++++
1 file changed, 5 insertions(+)
--
2.1.4
next reply other threads:[~2017-03-23 10:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 10:27 Nikolay Aleksandrov [this message]
2017-03-23 10:27 ` [PATCH net-next 1/2] net: bridge: allow SW learn to take over HW fdb entries Nikolay Aleksandrov via Bridge
2017-03-23 19:47 ` Ido Schimmel
2017-03-23 10:27 ` [PATCH net-next 2/2] net: bridge: allow to add externally learned entries from user-space Nikolay Aleksandrov
2017-03-23 19:47 ` Ido Schimmel
2017-03-23 12:48 ` [PATCH net-next 0/2] net: bridge: allow user-space to add ext learned entries Nikolay Aleksandrov via Bridge
2017-03-23 20:00 ` Ido Schimmel
2017-03-24 19:31 ` 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=1490264833-28867-1-git-send-email-nikolay@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=stephen@networkplumber.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).