From: Ido Schimmel <idosch@nvidia.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, petrm@nvidia.com, mlxsw@nvidia.com,
Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net-next 0/8] mlxsw: Various updates
Date: Wed, 4 May 2022 09:29:01 +0300 [thread overview]
Message-ID: <20220504062909.536194-1-idosch@nvidia.com> (raw)
Patches #1-#3 add missing topology diagrams in selftests and perform
small cleanups.
Patches #4-#5 make small adjustments in QoS configuration. See detailed
description in the commit messages.
Patches #6-#8 reduce the number of background EMAD transactions. The
driver periodically queries the device (via EMAD transactions) about
updates that cannot happen in certain situations. This can negatively
impact the latency of time critical transactions, as the device is busy
processing other transactions.
Before:
# perf stat -a -e devlink:devlink_hwmsg -- sleep 10
Performance counter stats for 'system wide':
452 devlink:devlink_hwmsg
10.009736160 seconds time elapsed
After:
# perf stat -a -e devlink:devlink_hwmsg -- sleep 10
Performance counter stats for 'system wide':
0 devlink:devlink_hwmsg
10.001726333 seconds time elapsed
Ido Schimmel (3):
mlxsw: spectrum_acl: Do not report activity for multicast routes
mlxsw: spectrum_switchdev: Only query FDB notifications when necessary
mlxsw: spectrum_router: Only query neighbour activity when necessary
Petr Machata (5):
selftests: mlxsw: bail_on_lldpad before installing the cleanup trap
selftests: router_vid_1: Add a diagram, fix coding style
selftests: router.sh: Add a diagram
mlxsw: spectrum_dcb: Do not warn about priority changes
mlxsw: Treat LLDP packets as control
.../mellanox/mlxsw/spectrum_acl_tcam.c | 5 ++-
.../ethernet/mellanox/mlxsw/spectrum_dcb.c | 13 --------
.../ethernet/mellanox/mlxsw/spectrum_router.c | 6 ++++
.../ethernet/mellanox/mlxsw/spectrum_router.h | 1 +
.../mellanox/mlxsw/spectrum_switchdev.c | 31 ++++++++++++-------
.../ethernet/mellanox/mlxsw/spectrum_trap.c | 2 +-
.../drivers/net/mlxsw/qos_headroom.sh | 4 +--
.../selftests/drivers/net/mlxsw/qos_pfc.sh | 4 +--
.../drivers/net/mlxsw/sch_red_ets.sh | 5 ++-
.../drivers/net/mlxsw/sch_red_root.sh | 5 ++-
.../selftests/net/forwarding/router.sh | 18 +++++++++++
.../selftests/net/forwarding/router_vid_1.sh | 27 +++++++++++++++-
12 files changed, 82 insertions(+), 39 deletions(-)
--
2.35.1
next reply other threads:[~2022-05-04 6:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 6:29 Ido Schimmel [this message]
2022-05-04 6:29 ` [PATCH net-next 1/8] selftests: mlxsw: bail_on_lldpad before installing the cleanup trap Ido Schimmel
2022-05-04 6:29 ` [PATCH net-next 2/8] selftests: router_vid_1: Add a diagram, fix coding style Ido Schimmel
2022-05-04 6:29 ` [PATCH net-next 3/8] selftests: router.sh: Add a diagram Ido Schimmel
2022-05-04 6:29 ` [PATCH net-next 4/8] mlxsw: spectrum_dcb: Do not warn about priority changes Ido Schimmel
2022-05-04 6:29 ` [PATCH net-next 5/8] mlxsw: Treat LLDP packets as control Ido Schimmel
2022-05-04 6:29 ` [PATCH net-next 6/8] mlxsw: spectrum_acl: Do not report activity for multicast routes Ido Schimmel
2022-05-04 6:29 ` [PATCH net-next 7/8] mlxsw: spectrum_switchdev: Only query FDB notifications when necessary Ido Schimmel
2022-05-04 6:29 ` [PATCH net-next 8/8] mlxsw: spectrum_router: Only query neighbour activity " Ido Schimmel
2022-05-04 10:30 ` [PATCH net-next 0/8] mlxsw: Various updates patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2021-06-08 12:44 Ido Schimmel
2021-06-08 21:50 ` patchwork-bot+netdevbpf
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=20220504062909.536194-1-idosch@nvidia.com \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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.