From: Petr Machata <petrm@nvidia.com>
To: <netdev@vger.kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Danielle Ratson <danieller@nvidia.com>,
Petr Machata <petrm@nvidia.com>, Ido Schimmel <idosch@nvidia.com>,
Amit Cohen <amcohen@nvidia.com>, <mlxsw@nvidia.com>
Subject: [PATCH net 0/5] mlxsw: Fixes
Date: Fri, 25 Oct 2024 16:26:24 +0200 [thread overview]
Message-ID: <cover.1729866134.git.petrm@nvidia.com> (raw)
In this patchset:
- Tx header should be pushed for each packet which is transmitted via
Spectrum ASICs. Patch #1 adds a missing call to skb_cow_head() to make
sure that there is both enough room to push the Tx header and that the
SKB header is not cloned and can be modified.
- Commit b5b60bb491b2 ("mlxsw: pci: Use page pool for Rx buffers
allocation") converted mlxsw to use page pool for Rx buffers allocation.
Sync for CPU and for device should be done for Rx pages. In patches #2
and #3, add the missing calls to sync pages for, respectively, CPU and
the device.
- Patch #4 then fixes a bug to IPv6 GRE forwarding offload. Patch #5 adds
a generic forwarding test that fails with mlxsw ports prior to the fix.
Amit Cohen (3):
mlxsw: spectrum_ptp: Add missing verification before pushing Tx header
mlxsw: pci: Sync Rx buffers for CPU
mlxsw: pci: Sync Rx buffers for device
Ido Schimmel (2):
mlxsw: spectrum_ipip: Fix memory leak when changing remote IPv6
address
selftests: forwarding: Add IPv6 GRE remote change tests
drivers/net/ethernet/mellanox/mlxsw/pci.c | 25 ++++--
.../ethernet/mellanox/mlxsw/spectrum_ipip.c | 26 +++++-
.../ethernet/mellanox/mlxsw/spectrum_ptp.c | 7 ++
.../selftests/net/forwarding/ip6gre_flat.sh | 14 ++++
.../net/forwarding/ip6gre_flat_key.sh | 14 ++++
.../net/forwarding/ip6gre_flat_keys.sh | 14 ++++
.../selftests/net/forwarding/ip6gre_hier.sh | 14 ++++
.../net/forwarding/ip6gre_hier_key.sh | 14 ++++
.../net/forwarding/ip6gre_hier_keys.sh | 14 ++++
.../selftests/net/forwarding/ip6gre_lib.sh | 80 +++++++++++++++++++
10 files changed, 212 insertions(+), 10 deletions(-)
--
2.45.0
next reply other threads:[~2024-10-25 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 14:26 Petr Machata [this message]
2024-10-25 14:26 ` [PATCH net 1/5] mlxsw: spectrum_ptp: Add missing verification before pushing Tx header Petr Machata
2024-10-25 14:26 ` [PATCH net 2/5] mlxsw: pci: Sync Rx buffers for CPU Petr Machata
2024-10-25 15:00 ` Alexander Lobakin
2024-10-27 7:29 ` Amit Cohen
2024-10-25 14:26 ` [PATCH net 3/5] mlxsw: pci: Sync Rx buffers for device Petr Machata
2024-10-25 15:02 ` Alexander Lobakin
2024-10-27 6:51 ` Amit Cohen
2024-10-29 15:12 ` Alexander Lobakin
2024-10-25 14:26 ` [PATCH net 4/5] mlxsw: spectrum_ipip: Fix memory leak when changing remote IPv6 address Petr Machata
2024-10-25 14:26 ` [PATCH net 5/5] selftests: forwarding: Add IPv6 GRE remote change tests Petr Machata
2024-10-31 1:30 ` [PATCH net 0/5] mlxsw: Fixes 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=cover.1729866134.git.petrm@nvidia.com \
--to=petrm@nvidia.com \
--cc=amcohen@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).