From: sfeldma@gmail.com
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, jiri@resnulli.us, siva.mannem.lnx@gmail.com,
pjonnala@broadcom.com, stephen@networkplumber.org,
roopa@cumulusnetworks.com, andrew@lunn.ch, f.fainelli@gmail.com,
vivien.didelot@savoirfairelinux.com
Subject: [PATCH net-next v3 0/7] bridge: don't age out externally added FDB entries
Date: Wed, 23 Sep 2015 08:39:13 -0700 [thread overview]
Message-ID: <1443022760-21301-1-git-send-email-sfeldma@gmail.com> (raw)
From: Scott Feldman <sfeldma@gmail.com>
v3: Per davem review: add del_timer_sync on rocker port remove.
v2: Per Jiri review comment: add BR_DEFAULT_AGEING_TIME to defines
Siva originally proposed skipping externally added FDB entries in the bridge's
FDB garbage collection func, and moving the ageing of externally added entries
to the port driver/device. This broke rocker, since rocker didn't have a
hardware (or software) mechanism for ageing out its learned FDB entries.
This patchset reintroduces Siva's bridge driver patch to skip externally added
entries and adds support in rocker so rocker can age out its own entries.
Rocker does this using a software timer similar to the bridge's FDB garbage
collection timer. Other switchdev devices/drivers can use this software timer
method or program the device to nofity aged-out entries to the driver.
Updated switchdev.txt documentation to reflect current state-of-the-art. This
removes one more XXX todo comment in switchdev.txt.
Scott Feldman (6):
rocker: track when FDB entry is touched.
rocker: store rocker_port in fdb key rather than pport
bridge: define some min/max/default ageing time constants
rocker: adding port ageing_time for ageing out FDB entries
rocker: add FDB cleanup timer
switchdev: update documentation on FDB ageing_time
Siva Mannem (1):
bridge: don't age externally added FDB entries
Documentation/networking/switchdev.txt | 24 +++++------
drivers/net/ethernet/rocker/rocker.c | 70 +++++++++++++++++++++++++++-----
include/linux/if_bridge.h | 6 +++
net/bridge/br_device.c | 2 +-
net/bridge/br_fdb.c | 2 +
5 files changed, 81 insertions(+), 23 deletions(-)
--
1.7.10.4
next reply other threads:[~2015-09-23 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 15:39 sfeldma [this message]
2015-09-23 15:39 ` [PATCH net-next v3 1/7] rocker: track when FDB entry is touched sfeldma
2015-09-23 15:39 ` [PATCH net-next v3 2/7] rocker: store rocker_port in fdb key rather than pport sfeldma
2015-09-23 15:39 ` [PATCH net-next v3 3/7] bridge: define some min/max/default ageing time constants sfeldma
2015-09-23 15:49 ` Jiri Pirko
2015-09-23 15:39 ` [PATCH net-next v3 4/7] rocker: adding port ageing_time for ageing out FDB entries sfeldma
2015-09-23 15:49 ` Jiri Pirko
2015-09-23 15:39 ` [PATCH net-next v3 5/7] rocker: add FDB cleanup timer sfeldma
2015-09-23 15:39 ` [PATCH net-next v3 6/7] bridge: don't age externally added FDB entries sfeldma
2015-09-23 15:39 ` [PATCH net-next v3 7/7] switchdev: update documentation on FDB ageing_time sfeldma
2015-09-23 21:36 ` [PATCH net-next v3 0/7] bridge: don't age out externally added FDB entries 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=1443022760-21301-1-git-send-email-sfeldma@gmail.com \
--to=sfeldma@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pjonnala@broadcom.com \
--cc=roopa@cumulusnetworks.com \
--cc=siva.mannem.lnx@gmail.com \
--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).