From: Kevin Hao <haokexin@gmail.com>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH net-next v2 0/4] net: Avoid the memory waste in some Ethernet drivers
Date: Sun, 31 Jan 2021 15:44:22 +0800 [thread overview]
Message-ID: <20210131074426.44154-1-haokexin@gmail.com> (raw)
Hi,
v2:
- Inline page_frag_alloc() and {netdev,napi}_alloc_frag()
- Adopt Vlastimil's suggestion and add his Acked-by
In the current implementation of napi_alloc_frag(), it doesn't have any
align guarantee for the returned buffer address. We would have to use
some ugly workarounds to make sure that we can get a align buffer
address for some Ethernet drivers. This patch series tries to introduce
some helper functions to make sure that an align buffer is returned.
Then we can drop the ugly workarounds and avoid the unnecessary memory
waste.
Kevin Hao (4):
mm: page_frag: Introduce page_frag_alloc_align()
net: Introduce {netdev,napi}_alloc_frag_align()
net: octeontx2: Use napi_alloc_frag_align() to avoid the memory waste
net: dpaa2: Use napi_alloc_frag_align() to avoid the memory waste
.../net/ethernet/freescale/dpaa2/dpaa2-eth.c | 3 +--
.../marvell/octeontx2/nic/otx2_common.c | 3 +--
include/linux/gfp.h | 12 +++++++--
include/linux/skbuff.h | 22 ++++++++++++++--
mm/page_alloc.c | 8 +++---
net/core/skbuff.c | 25 +++++++------------
6 files changed, 46 insertions(+), 27 deletions(-)
--
2.29.2
next reply other threads:[~2021-01-31 7:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 7:44 Kevin Hao [this message]
2021-01-31 7:44 ` [PATCH net-next v2 1/4] mm: page_frag: Introduce page_frag_alloc_align() Kevin Hao
2021-02-02 11:36 ` Ioana Ciornei
2021-02-02 11:48 ` Vlastimil Babka
2021-02-02 12:31 ` Ioana Ciornei
2021-02-02 16:19 ` Alexander Duyck
2021-02-04 6:40 ` Kevin Hao
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=20210131074426.44154-1-haokexin@gmail.com \
--to=haokexin@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
/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).