Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@xxxxxxxxxx>:
On Fri, 13 Oct 2023 14:48:20 +0800 you wrote:
> In [1] & [2] & [3], there are usecases for veth and virtio_net
> to use frag support in page pool to reduce memory usage, and it
> may request different frag size depending on the head/tail
> room space for xdp_frame/shinfo and mtu/packet size. When the
> requested frag size is large enough that a single page can not
> be split into more than one frag, using frag support only have
> performance penalty because of the extra frag count handling
> for frag support.
>
> [...]
Here is the summary with links:
- [net-next,v11,1/6] page_pool: fragment API support for 32-bit arch with 64-bit DMA
https://git.kernel.org/netdev/net-next/c/90de47f020db
- [net-next,v11,2/6] page_pool: unify frag_count handling in page_pool_is_last_frag()
(no matching commit)
- [net-next,v11,3/6] page_pool: remove PP_FLAG_PAGE_FRAG
(no matching commit)
- [net-next,v11,4/6] page_pool: introduce page_pool[_cache]_alloc() API
(no matching commit)
- [net-next,v11,5/6] page_pool: update document about fragment API
(no matching commit)
- [net-next,v11,6/6] net: veth: use newly added page pool API for veth with xdp
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
