From: patchwork-bot+netdevbpf@kernel.org
To: Tushar Vyavahare <tushar.vyavahare@intel.com>
Cc: netdev@vger.kernel.org, magnus.karlsson@intel.com,
maciej.fijalkowski@intel.com, stfomichev@gmail.com,
kernelxing@tencent.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, ast@kernel.org, daniel@iogearbox.net,
tirthendu.sarkar@intel.com, bpf@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/4] selftests/xsk: simplify UMEM setup
Date: Fri, 12 Jun 2026 22:40:11 +0000 [thread overview]
Message-ID: <178130401114.1275309.12520760927935385997.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260608130938.958793-1-tushar.vyavahare@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 8 Jun 2026 18:39:33 +0530 you wrote:
> This series simplifies UMEM handling in selftests/xsk.
>
> It centralizes UMEM property setup through helpers, moves UMEM ownership
> from ifobject to socket-owned state, and normalizes umem_size/mmap_size
> usage across the touched paths.
>
> v1 -> v2:
> - Applied helper usage consistently across the touched test paths.
> - Moved UMEM ownership to socket-owned state and switched to one
> heap-backed umem_real object at xsk_arr[0] with explicit reset/cleanup.
> - Kept shared-UMEM TX behavior unchanged via TX-local UMEM state
> copy/reset during TX configuration.
> - Folded pkt_generate() umem parameter removal into the ownership
> refactor patch (no standalone cleanup patch). [Maciej]
> - Updated mmap_size teardown handling to join the RX worker thread in
> single-thread mode before cleanup to synchronize UMEM mapping state.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/4] selftests/xsk: Introduce helpers for setting UMEM properties
https://git.kernel.org/netdev/net-next/c/19ff5c545750
- [net-next,v3,2/4] selftests/xsk: Move UMEM state from ifobject to xsk_socket_info
https://git.kernel.org/netdev/net-next/c/b17631032769
- [net-next,v3,3/4] selftests/xsk: Use umem_size() helper consistently
https://git.kernel.org/netdev/net-next/c/1a24fe421739
- [net-next,v3,4/4] selftests/xsk: Introduce mmap_size in umem struct
https://git.kernel.org/netdev/net-next/c/0fe61052acb0
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-06-12 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 13:09 [PATCH net-next v3 0/4] selftests/xsk: simplify UMEM setup Tushar Vyavahare
2026-06-08 13:09 ` [PATCH net-next v3 1/4] selftests/xsk: Introduce helpers for setting UMEM properties Tushar Vyavahare
2026-06-08 13:09 ` [PATCH net-next v3 2/4] selftests/xsk: Move UMEM state from ifobject to xsk_socket_info Tushar Vyavahare
2026-06-08 13:09 ` [PATCH net-next v3 3/4] selftests/xsk: Use umem_size() helper consistently Tushar Vyavahare
2026-06-08 13:09 ` [PATCH net-next v3 4/4] selftests/xsk: Introduce mmap_size in umem struct Tushar Vyavahare
2026-06-12 22:40 ` 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=178130401114.1275309.12520760927935385997.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stfomichev@gmail.com \
--cc=tirthendu.sarkar@intel.com \
--cc=tushar.vyavahare@intel.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