[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231215033011.12107-1-liangchen.linux@gmail.com>
Date: Fri, 15 Dec 2023 11:30:08 +0800
From: Liang Chen <liangchen.linux@...il.com>
To: davem@...emloft.net,
edumazet@...gle.com,
kuba@...nel.org,
pabeni@...hat.com,
hawk@...nel.org,
ilias.apalodimas@...aro.org,
linyunsheng@...wei.com
Cc: netdev@...r.kernel.org,
linux-mm@...ck.org,
jasowang@...hat.com,
almasrymina@...gle.com,
liangchen.linux@...il.com
Subject: [PATCH net-next v11 0/3] skbuff: Optimize SKB coalescing for page pool
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
Powered by blists - more mailing lists