From: patchwork-bot+netdevbpf@kernel.org
To: Bobby Eshleman <bobbyeshleman@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org, alexs@kernel.org,
si.yanteng@linux.dev, dzm91@hust.edu.cn,
michael.chan@broadcom.com, pavan.chebbi@broadcom.com,
joshwash@google.com, hramamurthy@google.com, saeedm@nvidia.com,
tariqt@nvidia.com, mbloch@nvidia.com, leon@kernel.org,
alexanderduyck@fb.com, kernel-team@meta.com,
daniel@iogearbox.net, razor@blackwall.org, shuah@kernel.org,
dw@davidwei.uk, sdf.kernel@gmail.com, mohsin.bashr@gmail.com,
willemb@google.com, jiang.kun2@zte.com.cn, xu.xin16@zte.com.cn,
wang.yaxin@zte.com.cn, netdev@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, sdf@fomichev.me,
almasrymina@google.com, bobbyeshleman@meta.com
Subject: Re: [PATCH net-next v5 0/8] net: devmem: support devmem with netkit devices
Date: Tue, 19 May 2026 02:10:41 +0000 [thread overview]
Message-ID: <177915664163.2054007.6384747943531037676.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260514-tcp-dm-netkit-v5-0-408c59b91e66@meta.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 14 May 2026 10:22:27 -0700 you wrote:
> This series enables TCP devmem TX through netkit devices.
>
> Netkit now supports queue leasing. A physical NIC's RX queue can be
> leased to a netkit guest interface inside a container namespace. This
> gives the container a devmem-capable data path on the RX side (bind-rx,
> etc...). On the TX side, the container process binds to its netkit guest
> interface and sends traffic that netkit redirects (via BPF or ip
> forwarding) to the physical NIC for DMA.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/8] net: convert netmem_tx flag to enum
https://git.kernel.org/netdev/net-next/c/7d3ab852dcd8
- [net-next,v5,2/8] net: netkit: declare NETMEM_TX_NO_DMA mode
https://git.kernel.org/netdev/net-next/c/6ce2bb048055
- [net-next,v5,3/8] net: devmem: support TX over NETMEM_TX_NO_DMA devices
https://git.kernel.org/netdev/net-next/c/1abe839b34ae
- [net-next,v5,4/8] selftests: drv-net: ncdevmem: add -n flag to skip NIC configuration
https://git.kernel.org/netdev/net-next/c/ecbdf3da7813
- [net-next,v5,5/8] selftests: drv-net: make attr _nk_guest_ifname public
https://git.kernel.org/netdev/net-next/c/28357ac667d4
- [net-next,v5,6/8] selftests: drv-net: refactor devmem command builders into lib module
https://git.kernel.org/netdev/net-next/c/6cac32fc3f1f
- [net-next,v5,7/8] selftests: drv-net: add primary_rx_redirect support to NetDrvContEnv
https://git.kernel.org/netdev/net-next/c/886a790b59f9
- [net-next,v5,8/8] selftests: drv-net: add netkit devmem tests
https://git.kernel.org/netdev/net-next/c/28c1cc999fbb
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-05-19 2:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 17:22 [PATCH net-next v5 0/8] net: devmem: support devmem with netkit devices Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 1/8] net: convert netmem_tx flag to enum Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 2/8] net: netkit: declare NETMEM_TX_NO_DMA mode Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 3/8] net: devmem: support TX over NETMEM_TX_NO_DMA devices Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 4/8] selftests: drv-net: ncdevmem: add -n flag to skip NIC configuration Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 5/8] selftests: drv-net: make attr _nk_guest_ifname public Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 6/8] selftests: drv-net: refactor devmem command builders into lib module Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 7/8] selftests: drv-net: add primary_rx_redirect support to NetDrvContEnv Bobby Eshleman
2026-05-14 17:22 ` [PATCH net-next v5 8/8] selftests: drv-net: add netkit devmem tests Bobby Eshleman
2026-05-19 2: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=177915664163.2054007.6384747943531037676.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexanderduyck@fb.com \
--cc=alexs@kernel.org \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=bobbyeshleman@gmail.com \
--cc=bobbyeshleman@meta.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dw@davidwei.uk \
--cc=dzm91@hust.edu.cn \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=jiang.kun2@zte.com.cn \
--cc=joshwash@google.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=michael.chan@broadcom.com \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=razor@blackwall.org \
--cc=saeedm@nvidia.com \
--cc=sdf.kernel@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=tariqt@nvidia.com \
--cc=wang.yaxin@zte.com.cn \
--cc=willemb@google.com \
--cc=xu.xin16@zte.com.cn \
/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