From: Jakub Kicinski <kuba@kernel.org>
To: Yunsheng Lin <linyunsheng@huawei.com>
Cc: <davem@davemloft.net>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, <bpf@vger.kernel.org>
Subject: Re: [PATCH net-next v10 0/6] introduce page_pool_alloc() related API
Date: Wed, 11 Oct 2023 08:36:17 -0700 [thread overview]
Message-ID: <20231011083617.61bba987@kernel.org> (raw)
In-Reply-To: <20230922091138.18014-1-linyunsheng@huawei.com>
On Fri, 22 Sep 2023 17:11:32 +0800 Yunsheng Lin wrote:
> In [1] & [2] & [3], there are usecases for veth and virtio_net
> 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 page pool API for the driver to
> allocate memory with least memory utilization and performance
> penalty when it doesn't know the size of memory it need
> beforehand.
Could you rebase & repost? Patches no longer apply :(
next prev parent reply other threads:[~2023-10-11 15:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 9:11 [PATCH net-next v10 0/6] introduce page_pool_alloc() related API Yunsheng Lin
2023-09-22 9:11 ` [PATCH net-next v10 1/6] page_pool: fragment API support for 32-bit arch with 64-bit DMA Yunsheng Lin
2023-10-03 7:45 ` Paolo Abeni
2023-10-03 9:40 ` Ilias Apalodimas
2023-10-03 22:12 ` Jakub Kicinski
2023-10-04 9:31 ` Alexander Lobakin
2023-10-08 9:36 ` Yunsheng Lin
2023-10-10 17:49 ` Alexander Lobakin
2023-09-22 9:11 ` [PATCH net-next v10 2/6] page_pool: unify frag_count handling in page_pool_is_last_frag() Yunsheng Lin
2023-09-22 9:11 ` [PATCH net-next v10 3/6] page_pool: remove PP_FLAG_PAGE_FRAG Yunsheng Lin
2023-09-22 9:11 ` [PATCH net-next v10 4/6] page_pool: introduce page_pool[_cache]_alloc() API Yunsheng Lin
2023-09-22 9:11 ` [PATCH net-next v10 5/6] page_pool: update document about fragment API Yunsheng Lin
2023-09-22 9:11 ` [PATCH net-next v10 6/6] net: veth: use newly added page pool API for veth with xdp Yunsheng Lin
2023-10-11 15:36 ` Jakub Kicinski [this message]
2023-10-12 11:34 ` [PATCH net-next v10 0/6] introduce page_pool_alloc() related API 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=20231011083617.61bba987@kernel.org \
--to=kuba@kernel.org \
--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=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linyunsheng@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).