From: Ido Schimmel <idosch@idosch.org>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, jiri@mellanox.com, petrm@mellanox.com,
alexpe@mellanox.com, mlxsw@mellanox.com,
Ido Schimmel <idosch@mellanox.com>
Subject: [PATCH net 0/7] mlxsw: Various fixes
Date: Tue, 11 Jun 2019 10:19:39 +0300 [thread overview]
Message-ID: <20190611071946.11089-1-idosch@idosch.org> (raw)
From: Ido Schimmel <idosch@mellanox.com>
This patchset contains various fixes for mlxsw.
Patch #1 fixes an hash polarization problem when a nexthop device is a
LAG device. This is caused by the fact that the same seed is used for
the LAG and ECMP hash functions.
Patch #2 fixes an issue in which the driver fails to refresh a nexthop
neighbour after it becomes dead. This prevents the nexthop from ever
being written to the adjacency table and used to forward traffic. Patch
#3 is a test case.
Patch #4 fixes a wrong extraction of TOS value in flower offload code.
Patch #5 is a test case.
Patch #6 works around a buffer issue in Spectrum-2 by reducing the
default sizes of the shared buffer pools.
Patch #7 prevents prio-tagged packets from entering the switch when PVID
is removed from the bridge port.
Please consider patches #2, #4 and #6 for 5.1.y
Ido Schimmel (4):
mlxsw: spectrum: Use different seeds for ECMP and LAG hash
mlxsw: spectrum_router: Refresh nexthop neighbour when it becomes dead
selftests: mlxsw: Test nexthop offload indication
mlxsw: spectrum: Disallow prio-tagged packets when PVID is removed
Jiri Pirko (2):
mlxsw: spectrum_flower: Fix TOS matching
selftests: tc_flower: Add TOS matching test
Petr Machata (1):
mlxsw: spectrum_buffers: Reduce pool size on Spectrum-2
drivers/net/ethernet/mellanox/mlxsw/reg.h | 2 +-
.../net/ethernet/mellanox/mlxsw/spectrum.c | 5 +-
.../mellanox/mlxsw/spectrum_buffers.c | 4 +-
.../ethernet/mellanox/mlxsw/spectrum_flower.c | 4 +-
.../ethernet/mellanox/mlxsw/spectrum_router.c | 73 ++++++++++++++++++-
.../selftests/drivers/net/mlxsw/rtnetlink.sh | 47 ++++++++++++
.../selftests/net/forwarding/tc_flower.sh | 36 ++++++++-
7 files changed, 161 insertions(+), 10 deletions(-)
--
2.20.1
next reply other threads:[~2019-06-11 7:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 7:19 Ido Schimmel [this message]
2019-06-11 7:19 ` [PATCH net 1/7] mlxsw: spectrum: Use different seeds for ECMP and LAG hash Ido Schimmel
2019-06-11 7:19 ` [PATCH net 2/7] mlxsw: spectrum_router: Refresh nexthop neighbour when it becomes dead Ido Schimmel
2019-06-11 7:19 ` [PATCH net 3/7] selftests: mlxsw: Test nexthop offload indication Ido Schimmel
2019-06-11 7:19 ` [PATCH net 4/7] mlxsw: spectrum_flower: Fix TOS matching Ido Schimmel
2019-06-11 7:19 ` [PATCH net 5/7] selftests: tc_flower: Add TOS matching test Ido Schimmel
2019-06-11 7:19 ` [PATCH net 6/7] mlxsw: spectrum_buffers: Reduce pool size on Spectrum-2 Ido Schimmel
2019-06-11 7:19 ` [PATCH net 7/7] mlxsw: spectrum: Disallow prio-tagged packets when PVID is removed Ido Schimmel
2019-06-12 18:08 ` [PATCH net 0/7] mlxsw: Various fixes David Miller
-- strict thread matches above, loose matches on Subject: below --
2019-04-10 6:58 Ido Schimmel
2019-04-10 18:58 ` 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=20190611071946.11089-1-idosch@idosch.org \
--to=idosch@idosch.org \
--cc=alexpe@mellanox.com \
--cc=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.