From: patchwork-bot+netdevbpf@kernel.org
To: Joe Damato <joe@dama.to>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, michael.chan@broadcom.com,
pavan.chebbi@broadcom.com, linux-kernel@vger.kernel.org,
leon@kernel.org
Subject: Re: [net-next v10 00/10] Add TSO map-once DMA helpers and bnxt SW USO support
Date: Sun, 12 Apr 2026 18:10:19 +0000 [thread overview]
Message-ID: <177601741954.3362600.9685441999214600166.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260408230607.2019402-1-joe@dama.to>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 8 Apr 2026 16:05:49 -0700 you wrote:
> Greetings:
>
> This series extends net/tso to add a data structure and some helpers allowing
> drivers to DMA map headers and packet payloads a single time. The helpers can
> then be used to reference slices of shared mapping for each segment. This
> helps to avoid the cost of repeated DMA mappings, especially on systems which
> use an IOMMU. N per-packet DMA maps are replaced with a single map for the
> entire GSO skb. As of v3, the series uses the DMA IOVA API (as suggested by
> Leon [1]) and provides a fallback path when an IOMMU is not in use. The DMA
> IOVA API provides even better efficiency than the v2; see below.
>
> [...]
Here is the summary with links:
- [net-next,v10,01/10] net: tso: Introduce tso_dma_map and helpers
https://git.kernel.org/netdev/net-next/c/82db77f6fb16
- [net-next,v10,02/10] net: bnxt: Export bnxt_xmit_get_cfa_action
https://git.kernel.org/netdev/net-next/c/268c63f2c6b2
- [net-next,v10,03/10] net: bnxt: Add a helper for tx_bd_ext
https://git.kernel.org/netdev/net-next/c/637237d3d93c
- [net-next,v10,04/10] net: bnxt: Use dma_unmap_len for TX completion unmapping
https://git.kernel.org/netdev/net-next/c/3cb430e62c83
- [net-next,v10,05/10] net: bnxt: Add TX inline buffer infrastructure
https://git.kernel.org/netdev/net-next/c/0c26a0e765e7
- [net-next,v10,06/10] net: bnxt: Add boilerplate GSO code
https://git.kernel.org/netdev/net-next/c/0440e27eedac
- [net-next,v10,07/10] net: bnxt: Implement software USO
https://git.kernel.org/netdev/net-next/c/cc5d90667db8
- [net-next,v10,08/10] net: bnxt: Add SW GSO completion and teardown support
https://git.kernel.org/netdev/net-next/c/87550ba2dc39
- [net-next,v10,09/10] net: bnxt: Dispatch to SW USO
https://git.kernel.org/netdev/net-next/c/28f2c22398fb
- [net-next,v10,10/10] selftests: drv-net: Add USO test
https://git.kernel.org/netdev/net-next/c/5d3b12d1a24b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-12 18:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 23:05 [net-next v10 00/10] Add TSO map-once DMA helpers and bnxt SW USO support Joe Damato
2026-04-08 23:05 ` [net-next v10 01/10] net: tso: Introduce tso_dma_map and helpers Joe Damato
2026-04-08 23:05 ` [net-next v10 02/10] net: bnxt: Export bnxt_xmit_get_cfa_action Joe Damato
2026-04-08 23:05 ` [net-next v10 03/10] net: bnxt: Add a helper for tx_bd_ext Joe Damato
2026-04-08 23:05 ` [net-next v10 04/10] net: bnxt: Use dma_unmap_len for TX completion unmapping Joe Damato
2026-04-08 23:05 ` [net-next v10 05/10] net: bnxt: Add TX inline buffer infrastructure Joe Damato
2026-04-08 23:05 ` [net-next v10 06/10] net: bnxt: Add boilerplate GSO code Joe Damato
2026-04-08 23:05 ` [net-next v10 07/10] net: bnxt: Implement software USO Joe Damato
2026-04-08 23:05 ` [net-next v10 08/10] net: bnxt: Add SW GSO completion and teardown support Joe Damato
2026-04-08 23:05 ` [net-next v10 09/10] net: bnxt: Dispatch to SW USO Joe Damato
2026-04-08 23:05 ` [net-next v10 10/10] selftests: drv-net: Add USO test Joe Damato
2026-04-12 18:10 ` patchwork-bot+netdevbpf [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=177601741954.3362600.9685441999214600166.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=joe@dama.to \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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