From: Marek Mietus <mmietus97@yahoo.com>
To: Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, sd@queasysnail.net, kuba@kernel.org
Cc: Jason@zx2c4.com
Subject: Re: [PATCH net-next v7 00/11] net: tunnel: introduce noref xmit flows for tunnels
Date: Thu, 12 Feb 2026 15:47:01 +0100 [thread overview]
Message-ID: <2e651cd7-e6e0-40ed-9e88-4cda9a96185d@yahoo.com> (raw)
In-Reply-To: <a8ea949a-ac36-4753-b8ab-f9a85004750a@redhat.com>
W dniu 3.02.2026 o 09:32, Paolo Abeni pisze:
> On 1/27/26 8:04 AM, Marek Mietus wrote:
>> Currently, tunnel xmit flows always take a reference on the dst_entry
>> for each xmitted packet. These atomic operations are redundant in some
>> flows.
>>
>> This patchset introduces the infrastructure required for converting
>> the tunnel xmit flows to noref, and converts them where possible.
>>
>> These changes improve tunnel performance, since less atomic operations
>> are used.
>>
>> There are already noref optimizations in both ipv4 and ip6.
>> (See __ip_queue_xmit, inet6_csk_xmit)
>> This patchset implements similar optimizations in ip and udp tunnels.
>>
>> Benchmarks:
>> I used a vxlan tunnel over a pair of veth peers and measured the average
>> throughput over multiple samples.
>>
>> I ran 100 samples on a clean build, and another 100 on a patched
>> build. Each sample ran for 120 seconds. These were my results:
>>
>> clean: 71.95 mb/sec, stddev = 1.71
>> patched: 74.92 mb/sec, stddev = 1.35
>
> Which H/W are you using? I've never seen so low figures in this decade,
> possibly not even in the previous one. Expected tput on not too
> obsoleted H/W is orders of magnitude higher, and we need more relevant
> figures.
>
Sorry for the late response.
I tested this on my i9-13900. The reason for these low figures is that I
used "iperf3 -l 2 -c <IP>" to measure throughput. I manually lowered the
packet length because I figured there might be some other factors at play
that could add noise to my measurements. I'll measure again without this
limit. From initial testing, it looks like this performance gain is also
achieved with the default packet size.
I'll include new measurements along with v8.
> Thanks,
>
> Paolo
>
>
prev parent reply other threads:[~2026-02-12 14:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260127070452.6581-1-mmietus97.ref@yahoo.com>
2026-01-27 7:04 ` [PATCH net-next v7 00/11] net: tunnel: introduce noref xmit flows for tunnels Marek Mietus
2026-01-27 7:04 ` [PATCH net-next v7 01/11] net: dst_cache: add noref versions for dst_cache Marek Mietus
2026-01-27 7:04 ` [PATCH net-next v7 02/11] net: tunnel: convert iptunnel_xmit to noref Marek Mietus
2026-02-03 8:21 ` Paolo Abeni
2026-02-04 16:52 ` Marek Mietus
2026-01-27 7:04 ` [PATCH net-next v7 03/11] net: tunnel: convert udp_tunnel{6,}_xmit_skb " Marek Mietus
2026-01-27 7:04 ` [PATCH net-next v7 04/11] net: tunnel: allow noref dsts in udp_tunnel{,6}_dst_lookup Marek Mietus
2026-01-30 0:56 ` Sabrina Dubroca
2026-01-27 7:04 ` [PATCH net-next v7 05/11] net: ovpn: convert ovpn_udp{4,6}_output to use a noref dst Marek Mietus
2026-01-27 7:04 ` [PATCH net-next v7 06/11] wireguard: socket: convert send{4,6} to use a noref dst when possible Marek Mietus
2026-01-27 7:04 ` [PATCH net-next v7 07/11] net: tunnel: convert ip_md_tunnel_xmit " Marek Mietus
2026-02-03 8:27 ` Paolo Abeni
2026-01-27 7:04 ` [PATCH net-next v7 08/11] net: tunnel: convert ip_tunnel_xmit " Marek Mietus
2026-01-27 7:04 ` [PATCH net-next v7 09/11] net: sctp: convert sctp_v{4,6}_xmit " Marek Mietus
2026-01-27 7:04 ` [PATCH net-next v7 10/11] net: sit: convert ipip6_tunnel_xmit to use a noref dst Marek Mietus
2026-01-27 7:04 ` [PATCH net-next v7 11/11] net: tipc: convert tipc_udp_xmit " Marek Mietus
2026-02-03 8:32 ` [PATCH net-next v7 00/11] net: tunnel: introduce noref xmit flows for tunnels Paolo Abeni
2026-02-12 14:47 ` Marek Mietus [this message]
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=2e651cd7-e6e0-40ed-9e88-4cda9a96185d@yahoo.com \
--to=mmietus97@yahoo.com \
--cc=Jason@zx2c4.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
/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