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>, <akpm@linux-foundation.org>,
<hawk@kernel.org>, <ilias.apalodimas@linaro.org>,
<peterz@infradead.org>, <yuzhao@google.com>,
<jhubbard@nvidia.com>, <will@kernel.org>, <willy@infradead.org>,
<jgg@ziepe.ca>, <mcroce@microsoft.com>, <willemb@google.com>,
<cong.wang@bytedance.com>, <pabeni@redhat.com>,
<haokexin@gmail.com>, <nogikh@google.com>, <elver@google.com>,
<memxor@gmail.com>, <vvs@virtuozzo.com>, <linux-mm@kvack.org>,
<edumazet@google.com>, <alexander.duyck@gmail.com>,
<dsahern@gmail.com>
Subject: [PATCH net-next -v5 0/4] some optimization for page pool
Date: Sat, 9 Oct 2021 17:37:20 +0800 [thread overview]
Message-ID: <20211009093724.10539-1-linyunsheng@huawei.com> (raw)
Patch 1: disable dma mapping support for 32-bit arch with 64-bit
DMA.
Patch 2 - 4: pp page frag tracking support
The small packet drop test show no notiable performance degradation
when page pool is disabled.
V5: Keep the put_page()/get_page() semantics.
V4:
1. Change error code to EOPNOTSUPP in patch 1.
2. Drop patch 2.
3. Use pp_frag_count to indicate if a pp page can be tracked,
to avoid breaking the mlx5 driver.
V3:
1. add patch 1/4/6/7.
2. use pp_magic to identify pp page uniquely too.
3. avoid unnecessary compound_head() calling.
V2: add patch 2, adjust the commit log accroding to the discussion
in V1, and fix a compiler error reported by kernel test robot.
Yunsheng Lin (4):
page_pool: disable dma mapping support for 32-bit arch with 64-bit DMA
page_pool: change BIAS_MAX to support incrementing
mm: introduce __get_page() and __put_page()
skbuff: keep track of pp page when pp_frag_count is used
include/linux/mm.h | 21 ++++++++++++++-------
include/linux/mm_types.h | 13 +------------
include/linux/skbuff.h | 30 ++++++++++++++++++++----------
include/net/page_pool.h | 36 ++++++++++++++++++++++++------------
mm/swap.c | 6 +++---
net/core/page_pool.c | 29 +++++++++--------------------
net/core/skbuff.c | 10 ++++++++--
7 files changed, 79 insertions(+), 66 deletions(-)
--
2.33.0
next reply other threads:[~2021-10-09 9:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 9:37 Yunsheng Lin [this message]
2021-10-09 9:37 ` [PATCH net-next -v5 1/4] page_pool: disable dma mapping support for 32-bit arch with 64-bit DMA Yunsheng Lin
2021-10-09 9:37 ` [PATCH net-next -v5 2/4] page_pool: change BIAS_MAX to support incrementing Yunsheng Lin
2021-10-09 9:37 ` [PATCH net-next -v5 3/4] mm: introduce __get_page() and __put_page() Yunsheng Lin
2021-10-09 19:49 ` John Hubbard
2021-10-09 20:15 ` Matthew Wilcox
2021-10-11 6:37 ` Yunsheng Lin
2021-10-11 12:25 ` Jesper Dangaard Brouer
2021-10-11 12:29 ` Ilias Apalodimas
2021-10-12 7:38 ` Yunsheng Lin
2021-10-12 7:49 ` Ilias Apalodimas
2021-10-09 9:37 ` [PATCH net-next -v5 4/4] skbuff: keep track of pp page when pp_frag_count is used Yunsheng Lin
2021-10-09 12:11 ` kernel test robot
2021-10-09 12:11 ` kernel test robot
2021-10-09 12:12 ` kernel test robot
2021-10-09 12:12 ` kernel test robot
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=20211009093724.10539-1-linyunsheng@huawei.com \
--to=linyunsheng@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--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=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxarm@openeuler.org \
--cc=mcroce@microsoft.com \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nogikh@google.com \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=vvs@virtuozzo.com \
--cc=will@kernel.org \
--cc=willemb@google.com \
--cc=willy@infradead.org \
--cc=yuzhao@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.