From: Liang Chen <liangchen.linux@gmail.com>
To: hawk@kernel.org, horms@kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linyunsheng@huawei.com
Cc: ilias.apalodimas@linaro.org, daniel@iogearbox.net,
ast@kernel.org, netdev@vger.kernel.org,
liangchen.linux@gmail.com
Subject: [RFC PATCH net-next v3 0/2] net: veth: Optimizing page pool usage
Date: Wed, 16 Aug 2023 20:30:27 +0800 [thread overview]
Message-ID: <20230816123029.20339-1-liangchen.linux@gmail.com> (raw)
Page pool is supported for veth, but at the moment pages are not properly
recyled for XDP_TX and XDP_REDIRECT. That prevents veth xdp from fully
leveraging the advantages of the page pool. So this RFC patchset is mainly
to make recycling work for those cases. With that in place, it can be
further optimized by utilizing the napi skb cache. Detailed figures are
presented in each commit message, and together they demonstrate a quite
noticeable improvement.
Changes from v2:
- refactor the code to make it more readable
- make use of the napi skb cache for further optimization
- take the Page pool creation error handling patch out for separate
submission
Liang Chen (2):
net: veth: Improving page pool recycling
net: veth: Optimizing skb reuse in NAPI Context
drivers/net/veth.c | 66 ++++++++++++++++++++++++++++++++++++++++------
net/core/skbuff.c | 1 +
2 files changed, 59 insertions(+), 8 deletions(-)
--
2.40.1
next reply other threads:[~2023-08-16 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 12:30 Liang Chen [this message]
2023-08-16 12:30 ` [RFC PATCH net-next v3 1/2] net: veth: Improving page pool recycling Liang Chen
2023-08-16 12:30 ` [RFC PATCH net-next v3 2/2] net: veth: Optimizing skb reuse in NAPI Context Liang Chen
2023-08-21 14:21 ` [RFC PATCH net-next v3 0/2] net: veth: Optimizing page pool usage Jesper Dangaard Brouer
2023-08-21 21:54 ` Jesper Dangaard Brouer
2023-08-22 12:24 ` Yunsheng Lin
2023-08-22 13:05 ` Jesper Dangaard Brouer
2023-08-22 18:13 ` Jesper Dangaard Brouer
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=20230816123029.20339-1-liangchen.linux@gmail.com \
--to=liangchen.linux@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=linyunsheng@huawei.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).