From: Yunsheng Lin <linyunsheng@huawei.com>
To: <davem@davemloft.net>, <kuba@kernel.org>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@openeuler.org>, <hawk@kernel.org>,
<ilias.apalodimas@linaro.org>, <jonathan.lemon@gmail.com>,
<alobakin@pm.me>, <willemb@google.com>, <cong.wang@bytedance.com>,
<pabeni@redhat.com>, <haokexin@gmail.com>, <nogikh@google.com>,
<elver@google.com>, <memxor@gmail.com>, <edumazet@google.com>,
<alexander.duyck@gmail.com>, <dsahern@gmail.com>
Subject: [PATCH net-next 0/2] some optimization for page pool
Date: Mon, 30 Aug 2021 09:18:08 +0800 [thread overview]
Message-ID: <1630286290-43714-1-git-send-email-linyunsheng@huawei.com> (raw)
Patch 1: support non-split page when PP_FLAG_PAGE_FRAG is set.
Patch 1: keep track of pp page when __skb_frag_ref() is called.
Yunshene Lin (2):
page_pool: support non-split page with PP_FLAG_PAGE_FRAG
skbuff: keep track of pp page when __skb_frag_ref() is called
include/linux/skbuff.h | 13 ++++++++++++-
include/net/page_pool.h | 23 +++++++++++++++++++++++
net/core/page_pool.c | 24 +++++++++---------------
3 files changed, 44 insertions(+), 16 deletions(-)
--
2.7.4
next reply other threads:[~2021-08-30 1:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 1:18 Yunsheng Lin [this message]
2021-08-30 1:18 ` [PATCH net-next 1/2] page_pool: support non-split page with PP_FLAG_PAGE_FRAG Yunsheng Lin
2021-08-30 15:05 ` Alexander Duyck
2021-08-31 6:14 ` Yunsheng Lin
2021-08-31 13:43 ` Alexander Duyck
2021-08-30 1:18 ` [PATCH net-next 2/2] skbuff: keep track of pp page when __skb_frag_ref() is called Yunsheng Lin
2021-08-30 4:50 ` kernel test robot
2021-08-30 4:50 ` kernel test robot
2021-08-30 15:14 ` Alexander Duyck
2021-08-31 7:20 ` Yunsheng Lin
2021-08-31 14:30 ` Alexander Duyck
2021-09-01 3:10 ` 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=1630286290-43714-1-git-send-email-linyunsheng@huawei.com \
--to=linyunsheng@huawei.com \
--cc=alexander.duyck@gmail.com \
--cc=alobakin@pm.me \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=haokexin@gmail.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nogikh@google.com \
--cc=pabeni@redhat.com \
--cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.