linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Liang Chen <liangchen.linux@gmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, hawk@kernel.org, ilias.apalodimas@linaro.org,
	linyunsheng@huawei.com
Cc: netdev@vger.kernel.org, linux-mm@kvack.org, jasowang@redhat.com,
	almasrymina@google.com, liangchen.linux@gmail.com
Subject: [PATCH net-next v11 0/3] skbuff: Optimize SKB coalescing for page pool
Date: Fri, 15 Dec 2023 11:30:08 +0800	[thread overview]
Message-ID: <20231215033011.12107-1-liangchen.linux@gmail.com> (raw)

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.

This patchset aims to optimize this scenario and enable coalescing of this
particular combination. That also involves supporting multiple users
referencing the same fragment of a pp page to accomondate the need to
increment the "from" SKB page's pp page reference count.


Changes from v10:
- re-number patches to 1/3, 2/3, 3/3

Changes from v9:
- patch 1 was already applied
- imporve description for patch 2
- make sure skb_pp_frag_ref only work for pp aware skbs



Liang Chen (3):
  page_pool: halve BIAS_MAX for multiple user references of a fragment
  skbuff: Add a function to check if a page belongs to page_pool
  skbuff: Optimization of SKB coalescing for page pool

 include/net/page_pool/helpers.h |  5 +++
 net/core/page_pool.c            |  2 +-
 net/core/skbuff.c               | 59 +++++++++++++++++++++++++--------
 3 files changed, 52 insertions(+), 14 deletions(-)

-- 
2.31.1



             reply	other threads:[~2023-12-15  3:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15  3:30 Liang Chen [this message]
2023-12-15  3:30 ` [PATCH net-next v11 1/3] page_pool: halve BIAS_MAX for multiple user references of a fragment Liang Chen
2023-12-15  3:30 ` [PATCH net-next v11 2/3] skbuff: Add a function to check if a page belongs to page_pool Liang Chen
2023-12-15  3:30 ` [PATCH net-next v11 3/3] skbuff: Optimization of SKB coalescing for page pool Liang Chen
2023-12-17 11:01 ` [PATCH net-next v11 0/3] skbuff: Optimize " patchwork-bot+netdevbpf

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=20231215033011.12107-1-liangchen.linux@gmail.com \
    --to=liangchen.linux@gmail.com \
    --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=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