From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, idosch@mellanox.com, eladr@mellanox.com,
mlxsw@mellanox.com
Subject: [patch net-next 0/8] mlxsw: cleanup neigh handling
Date: Mon, 6 Feb 2017 16:20:09 +0100 [thread overview]
Message-ID: <1486394417-8011-1-git-send-email-jiri@resnulli.us> (raw)
From: Jiri Pirko <jiri@mellanox.com>
Ido says:
This series addresses long standing issues in the mlxsw driver
concerning neighbour reflection. It also prepares the code for follow-up
changes dealing with proper resource cleanup and nexthop reflection.
The first two patches convert the neighbour reflection code to use an
ordered workqueue, to prevent re-ordering of NEIGH_UPDATE events that
may happen following subsequent patches.
The third to fifth patches remove the ndo_neigh_{construct,destroy}
entry points from the driver, thereby relying only on NEIGH_UPDATE
events for neighbour reflection. This simplifies the code considerably.
Last patches are fallout and adjust nits in the code I noticed while
going over it.
Ido Schimmel (8):
mlxsw: core: Queue work immediately instead of delaying it
mlxsw: spectrum_router: Use ordered workqueue for neigh updates
mlxsw: spectrum_router: Remove unused variable
mlxsw: spectrum_router: Simplify neighbour reflection
net: remove ndo_neigh_{construct,destroy} from stacked devices
mlxsw: spectrum_router: Remove redundant check
mlxsw: spectrum_router: Don't read 'nud_state' without lock
mlxsw: spectrum_router: Fix typo in comment
drivers/net/bonding/bond_main.c | 2 -
drivers/net/ethernet/mellanox/mlxsw/core.c | 6 +-
drivers/net/ethernet/mellanox/mlxsw/core.h | 2 +-
drivers/net/ethernet/mellanox/mlxsw/spectrum.c | 2 -
drivers/net/ethernet/mellanox/mlxsw/spectrum.h | 4 -
.../net/ethernet/mellanox/mlxsw/spectrum_router.c | 287 +++++++++++----------
drivers/net/team/team.c | 2 -
include/linux/netdevice.h | 4 -
net/8021q/vlan_dev.c | 2 -
net/bridge/br_device.c | 2 -
net/core/dev.c | 44 ----
11 files changed, 148 insertions(+), 209 deletions(-)
--
2.7.4
next reply other threads:[~2017-02-06 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 15:20 Jiri Pirko [this message]
2017-02-06 15:20 ` [patch net-next 1/8] mlxsw: core: Queue work immediately instead of delaying it Jiri Pirko
2017-02-06 15:20 ` [patch net-next 2/8] mlxsw: spectrum_router: Use ordered workqueue for neigh updates Jiri Pirko
2017-02-06 15:20 ` [patch net-next 3/8] mlxsw: spectrum_router: Remove unused variable Jiri Pirko
2017-02-06 15:20 ` [patch net-next 4/8] mlxsw: spectrum_router: Simplify neighbour reflection Jiri Pirko
2017-02-06 15:20 ` [patch net-next 5/8] net: remove ndo_neigh_{construct,destroy} from stacked devices Jiri Pirko
2017-02-06 15:20 ` [patch net-next 6/8] mlxsw: spectrum_router: Remove redundant check Jiri Pirko
2017-02-06 15:20 ` [patch net-next 7/8] mlxsw: spectrum_router: Don't read 'nud_state' without lock Jiri Pirko
2017-02-06 15:20 ` [patch net-next 8/8] mlxsw: spectrum_router: Fix typo in comment Jiri Pirko
2017-02-06 16:28 ` [patch net-next 0/8] mlxsw: cleanup neigh handling David Miller
2017-02-07 9:45 ` Jiri Pirko
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=1486394417-8011-1-git-send-email-jiri@resnulli.us \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=eladr@mellanox.com \
--cc=idosch@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.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).