linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Liang Chen <liangchen.linux@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, hawk@kernel.org, ilias.apalodimas@linaro.org,
	linyunsheng@huawei.com, netdev@vger.kernel.org,
	linux-mm@kvack.org, jasowang@redhat.com, almasrymina@google.com
Subject: Re: [PATCH net-next v9 0/4] skbuff: Optimize SKB coalescing for page pool
Date: Thu, 14 Dec 2023 03:00:26 +0000	[thread overview]
Message-ID: <170252282616.11535.4456947354721331080.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231212044614.42733-1-liangchen.linux@gmail.com>

Hello:

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

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




      parent reply	other threads:[~2023-12-14  3:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12  4:46 Liang Chen
2023-12-12  4:46 ` [PATCH net-next v9 1/4] page_pool: transition to reference count management after page draining Liang Chen
2023-12-13  1:53   ` Mina Almasry
2023-12-12  4:46 ` [PATCH net-next v9 2/4] page_pool: halve BIAS_MAX for multiple user references of a fragment Liang Chen
2023-12-13  1:51   ` Mina Almasry
2023-12-13 11:38   ` Ilias Apalodimas
2023-12-14  3:42     ` Liang Chen
2023-12-12  4:46 ` [PATCH net-next v9 3/4] skbuff: Add a function to check if a page belongs to page_pool Liang Chen
2023-12-13  1:50   ` Mina Almasry
2023-12-12  4:46 ` [PATCH net-next v9 4/4] skbuff: Optimization of SKB coalescing for page pool Liang Chen
2023-12-13  1:49   ` Mina Almasry
2023-12-13  2:37     ` Liang Chen
2023-12-13  2:49       ` Mina Almasry
2023-12-14  3:00 ` 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=170252282616.11535.4456947354721331080.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=almasrymina@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jasowang@redhat.com \
    --cc=kuba@kernel.org \
    --cc=liangchen.linux@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=linyunsheng@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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