From: Yunsheng Lin <linyunsheng@huawei.com>
To: <davem@davemloft.net>, <kuba@kernel.org>, <pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Yunsheng Lin <linyunsheng@huawei.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>, <bpf@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>
Subject: [RFC 0/3] support non-frag page for page_pool_alloc_frag()
Date: Tue, 16 May 2023 20:47:58 +0800 [thread overview]
Message-ID: <20230516124801.2465-1-linyunsheng@huawei.com> (raw)
In [1], there is a use case 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.
So this patchset provides a way for user to fail back to
non-frag page depending on the user's request.
1. https://patchwork.kernel.org/project/netdevbpf/patch/d3ae6bd3537fbce379382ac6a42f67e22f27ece2.1683896626.git.lorenzo@kernel.org/
Yunsheng Lin (3):
page_pool: unify frag page and non-frag page handling
page_pool: support non-frag page for page_pool_alloc_frag()
page_pool: introduce 'struct page_pool_frag'
.../net/ethernet/hisilicon/hns3/hns3_enet.c | 16 +++---
drivers/net/wireless/mediatek/mt76/mt76.h | 9 ++--
include/net/page_pool.h | 51 ++++++++++++++-----
net/core/page_pool.c | 45 +++++++++++-----
4 files changed, 86 insertions(+), 35 deletions(-)
--
2.33.0
next reply other threads:[~2023-05-16 12:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 12:47 Yunsheng Lin [this message]
2023-05-16 12:47 ` [RFC 1/3] page_pool: unify frag page and non-frag page handling Yunsheng Lin
2023-05-16 12:48 ` [RFC 2/3] page_pool: support non-frag page for page_pool_alloc_frag() Yunsheng Lin
2023-05-16 12:48 ` [RFC 3/3] page_pool: introduce 'struct page_pool_frag' Yunsheng Lin
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=20230516124801.2465-1-linyunsheng@huawei.com \
--to=linyunsheng@huawei.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.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
all inboxes | Powered by JetHome®