netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Machata <petrm@mellanox.com>
To: netdev@vger.kernel.org
Cc: ivecera@redhat.com, davem@davemloft.net,
	stephen@networkplumber.org, andrew@lunn.ch,
	vivien.didelot@savoirfairelinux.com, f.fainelli@gmail.com,
	jiri@resnulli.us
Subject: [PATCH net-next 0/2] bridge: FDB: Notify about removal of non-user-added entries
Date: Tue, 01 May 2018 19:04:19 +0200	[thread overview]
Message-ID: <cover.1525194039.git.petrm@mellanox.com> (raw)

Device drivers may generally need to keep in sync with bridge's FDB. In
particular, for its offload of tc mirror action where the mirrored-to
device is a gretap device, mlxsw needs to listen to a number of events.
SWITCHDEV_FDB_{ADD,DEL}_TO_DEVICE would be a natural notification to
listen to in order to keep up with FDB updates.

However, for removal of FDB entries added due to device activity (as
opposed to explicit addition through "bridge fdb add" or similar), there
are no notifications.

Thus in patch #1, add the "added_by_user" field to switchdev
notifications sent for FDB activity. Adapt drivers to ignore activity on
non-user-added entries, to maintain the current behavior. Specifically
in case of mlxsw, allow mlxsw_sp_span_respin() call for any and all FDB
updates.

In patch #2, change the bridge driver to actually emit notifications for
these FDB entries. Take care not to send notification for bridge
updates that itself originate in SWITCHDEV_FDB_*_TO_BRIDGE events.

Petr Machata (2):
  switchdev: Add fdb.added_by_user to switchdev notifications
  net: bridge: Notify about !added_by_user FDB entries

 .../ethernet/mellanox/mlxsw/spectrum_switchdev.c   |  4 +++
 drivers/net/ethernet/rocker/rocker_main.c          |  2 ++
 include/net/switchdev.h                            |  1 +
 net/bridge/br.c                                    |  4 +--
 net/bridge/br_fdb.c                                | 40 +++++++++++++++-------
 net/bridge/br_private.h                            |  4 +--
 net/bridge/br_switchdev.c                          | 12 ++++---
 net/dsa/slave.c                                    |  5 ++-
 8 files changed, 50 insertions(+), 22 deletions(-)

-- 
2.4.11

             reply	other threads:[~2018-05-01 17:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01 17:04 Petr Machata [this message]
2018-05-01 17:04 ` [PATCH net-next 1/2] switchdev: Add fdb.added_by_user to switchdev notifications Petr Machata
2018-05-01 17:49   ` Nikolay Aleksandrov
2018-05-01 17:04 ` [PATCH net-next 2/2] net: bridge: Notify about !added_by_user FDB entries Petr Machata
2018-05-01 17:49   ` Nikolay Aleksandrov
2018-05-01 22:33     ` Petr Machata
2018-05-01 17:54 ` [PATCH net-next 0/2] bridge: FDB: Notify about removal of non-user-added entries Andrew Lunn
2018-05-01 22:27   ` Petr Machata

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=cover.1525194039.git.petrm@mellanox.com \
    --to=petrm@mellanox.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=ivecera@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=vivien.didelot@savoirfairelinux.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;
as well as URLs for NNTP newsgroup(s).