Re: [PATCH net-next v9 0/4] skbuff: Optimize SKB coalescing for page pool

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@xxxxxxxxxx>:

On Tue, 12 Dec 2023 12:46:10 +0800 you wrote:
> The combination of the following condition was excluded from skb coalescing:
> 
> from->pp_recycle = 1
> from->cloned = 1
> to->pp_recycle = 1
> 
> With page pool in use, this combination can be quite common(ex.
> NetworkMananger may lead to the additional packet_type being registered,
> thus the cloning). In scenarios with a higher number of small packets, it
> can significantly affect the success rate of coalescing.
> 
> [...]

Here is the summary with links:
  - [net-next,v9,1/4] page_pool: transition to reference count management after page draining
    https://git.kernel.org/netdev/net-next/c/0a149ab78ee2
  - [net-next,v9,2/4] page_pool: halve BIAS_MAX for multiple user references of a fragment
    (no matching commit)
  - [net-next,v9,3/4] skbuff: Add a function to check if a page belongs to page_pool
    (no matching commit)
  - [net-next,v9,4/4] skbuff: Optimization of SKB coalescing for page pool
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html






[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux