From: David Miller <davem@davemloft.net>
To: sfeldma@gmail.com
Cc: netdev@vger.kernel.org, jiri@resnulli.us,
roopa@cumulusnetworks.com, john.r.fastabend@intel.com,
andrew@lunn.ch, f.fainelli@gmail.com, linux@roeck-us.net,
stephen@networkplumber.org
Subject: Re: [PATCH net-next] bridge: del external_learned fdbs from device on flush or ageout
Date: Mon, 15 Jun 2015 17:09:24 -0700 (PDT) [thread overview]
Message-ID: <20150615.170924.2212463704435329039.davem@davemloft.net> (raw)
In-Reply-To: <1434306791-43364-1-git-send-email-sfeldma@gmail.com>
From: sfeldma@gmail.com
Date: Sun, 14 Jun 2015 11:33:11 -0700
> From: Scott Feldman <sfeldma@gmail.com>
>
> We need to delete from offload the device externally learnded fdbs when any
> one of these events happen:
>
> 1) Bridge ages out fdb. (When bridge is doing ageing vs. device doing
> ageing. If device is doing ageing, it would send SWITCHDEV_FDB_DEL
> directly).
>
> 2) STP state change flushes fdbs on port.
>
> 3) User uses sysfs interface to flush fdbs from bridge or bridge port:
>
> echo 1 >/sys/class/net/BR_DEV/bridge/flush
> echo 1 >/sys/class/net/BR_PORT/brport/flush
>
> 4) Offload driver send event SWITCHDEV_FDB_DEL to delete fdb entry.
>
> For rocker, we can now get called to delete fdb entry in wait and nowait
> contexts, so set NOWAIT flag when deleting fdb entry.
>
> Signed-off-by: Scott Feldman <sfeldma@gmail.com>
Applied, thanks Scott.
prev parent reply other threads:[~2015-06-16 0:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 18:33 [PATCH net-next] bridge: del external_learned fdbs from device on flush or ageout sfeldma
2015-06-14 22:14 ` Rami Rosen
2015-06-14 23:19 ` Scott Feldman
2015-06-15 6:23 ` Rami Rosen
2015-06-16 0:09 ` David Miller [this message]
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=20150615.170924.2212463704435329039.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=jiri@resnulli.us \
--cc=john.r.fastabend@intel.com \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@gmail.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).