From: Jakub Kicinski <kuba@kernel.org>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
Yunsheng Lin <linyunsheng@huawei.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, ast@kernel.org,
daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com
Subject: Re: [RFC net-next] net: veth: reduce page_pool memory footprint using half page per-buffer
Date: Wed, 17 May 2023 07:58:49 -0700 [thread overview]
Message-ID: <20230517075849.2af98d72@kernel.org> (raw)
In-Reply-To: <ZGQJKRfuf4+av/MD@lore-desk>
On Wed, 17 May 2023 00:52:25 +0200 Lorenzo Bianconi wrote:
> I am testing this RFC patch in the scenario reported below:
>
> iperf tcp tx --> veth0 --> veth1 (xdp_pass) --> iperf tcp rx
>
> - 6.4.0-rc1 net-next:
> MTU 1500B: ~ 7.07 Gbps
> MTU 8000B: ~ 14.7 Gbps
>
> - 6.4.0-rc1 net-next + page_pool frag support in veth:
> MTU 1500B: ~ 8.57 Gbps
> MTU 8000B: ~ 14.5 Gbps
>
> side note: it seems there is a regression between 6.2.15 and 6.4.0-rc1 net-next
> (even without latest veth page_pool patches) in the throughput I can get in the
> scenario above, but I have not looked into it yet.
>
> - 6.2.15:
> MTU 1500B: ~ 7.91 Gbps
> MTU 8000B: ~ 14.1 Gbps
>
> - 6.4.0-rc1 net-next w/o commits [0],[1],[2]
> MTU 1500B: ~ 6.38 Gbps
> MTU 8000B: ~ 13.2 Gbps
If the benchmark is iperf, wouldn't working towards preserving GSO
status across XDP (assuming prog is multi-buf-capable) be the most
beneficial optimization?
next prev parent reply other threads:[~2023-05-17 14:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 13:08 [RFC net-next] net: veth: reduce page_pool memory footprint using half page per-buffer Lorenzo Bianconi
2023-05-12 13:43 ` Alexander Lobakin
2023-05-12 14:14 ` Lorenzo Bianconi
2023-05-15 16:36 ` Alexander Lobakin
2023-05-15 11:10 ` Yunsheng Lin
2023-05-15 11:24 ` Lorenzo Bianconi
2023-05-15 13:11 ` Maciej Fijalkowski
2023-05-16 22:52 ` Lorenzo Bianconi
2023-05-17 9:41 ` Yunsheng Lin
2023-05-17 14:17 ` Lorenzo Bianconi
2023-05-18 1:16 ` Yunsheng Lin
2023-05-17 14:58 ` Jakub Kicinski [this message]
2023-05-16 12:55 ` Yunsheng Lin
2023-05-16 16:11 ` 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=20230517075849.2af98d72@kernel.org \
--to=kuba@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=linyunsheng@huawei.com \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=maciej.fijalkowski@intel.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 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.