netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Aleksandrov <razor@blackwall.org>
To: netdev@vger.kernel.org
Cc: dsahern@gmail.com, stephen@networkplumber.org, roopa@nvidia.com,
	Nikolay Aleksandrov <razor@blackwall.org>
Subject: [PATCH iproute2-next 00/10] bridge: fdb: add extended flush support
Date: Wed,  8 Jun 2022 15:29:11 +0300	[thread overview]
Message-ID: <20220608122921.3962382-1-razor@blackwall.org> (raw)

Hi,
This set adds support for the new bulk delete flag to allow fdb flushing
for specific entries which are matched based on the supplied options.
The new bridge fdb subcommand is "flush", and as can be seen from the
commits it allows to delete entries based on many different criteria:
 - matching vlan
 - matching port
 - matching all sorts of flags (combinations are allowed)

There are also examples for each option in the respective commit messages.

Examples:
$ bridge fdb flush dev swp2 master vlan 100 dynamic
 [ delete all dynamic entries with port swp2 and vlan 100 ]
$ bridge fdb flush dev br0 vlan 1 static
 [ delete all static entries in br0's fdb table ]
$ bridge fdb flush dev swp2 master extern_learn nosticky
 [ delete all entries with port swp2 which have extern_learn set and
   don't have the sticky flag set ]
$ bridge fdb flush dev br0 brport br0 vlan 100 permanent
 [ delete all entries pointing to the bridge itself with vlan 100 ]
$ bridge fdb flush dev swp2 master nostatic nooffloaded
 [ delete all entries with port swp2 which are not static and not
   offloaded ]

If keyword is specified and after that nokeyword is specified obviously
the nokeyword would override keyword.

Thanks,
 Nik

Nikolay Aleksandrov (10):
  bridge: fdb: add new flush command
  bridge: fdb: add flush vlan matching
  bridge: fdb: add flush port matching
  bridge: fdb: add flush [no]permanent entry matching
  bridge: fdb: add flush [no]static entry matching
  bridge: fdb: add flush [no]dynamic entry matching
  bridge: fdb: add flush [no]added_by_user entry matching
  bridge: fdb: add flush [no]extern_learn entry matching
  bridge: fdb: add flush [no]sticky entry matching
  bridge: fdb: add flush [no]offloaded entry matching

 bridge/fdb.c      | 142 +++++++++++++++++++++++++++++++++++++++++++++-
 man/man8/bridge.8 |  83 +++++++++++++++++++++++++++
 2 files changed, 224 insertions(+), 1 deletion(-)

-- 
2.35.1


             reply	other threads:[~2022-06-08 12:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 12:29 Nikolay Aleksandrov [this message]
2022-06-08 12:29 ` [PATCH iproute2-next 01/10] bridge: fdb: add new flush command Nikolay Aleksandrov
2022-06-08 12:29 ` [PATCH iproute2-next 02/10] bridge: fdb: add flush vlan matching Nikolay Aleksandrov
2022-06-08 12:29 ` [PATCH iproute2-next 03/10] bridge: fdb: add flush port matching Nikolay Aleksandrov
2022-06-08 12:29 ` [PATCH iproute2-next 04/10] bridge: fdb: add flush [no]permanent entry matching Nikolay Aleksandrov
2022-06-08 12:29 ` [PATCH iproute2-next 05/10] bridge: fdb: add flush [no]static " Nikolay Aleksandrov
2022-06-08 12:29 ` [PATCH iproute2-next 06/10] bridge: fdb: add flush [no]dynamic " Nikolay Aleksandrov
2022-06-08 12:29 ` [PATCH iproute2-next 07/10] bridge: fdb: add flush [no]added_by_user " Nikolay Aleksandrov
2022-06-08 12:29 ` [PATCH iproute2-next 08/10] bridge: fdb: add flush [no]extern_learn " Nikolay Aleksandrov
2022-06-08 12:29 ` [PATCH iproute2-next 09/10] bridge: fdb: add flush [no]sticky " Nikolay Aleksandrov
2022-06-08 12:29 ` [PATCH iproute2-next 10/10] bridge: fdb: add flush [no]offloaded " Nikolay Aleksandrov
2022-06-10 15:10 ` [PATCH iproute2-next 00/10] bridge: fdb: add extended flush support patchwork-bot+netdevbpf

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=20220608122921.3962382-1-razor@blackwall.org \
    --to=razor@blackwall.org \
    --cc=dsahern@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@nvidia.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).