From: Sabrina Dubroca <sd@queasysnail.net>
To: Marek Mietus <mmietus97@yahoo.com>
Cc: netdev@vger.kernel.org, antonio@openvpn.net, kuba@kernel.org,
openvpn-devel@lists.sourceforge.net
Subject: Re: [PATCH net-next v2 3/3] net: ovpn: use new noref xmit flow in ovpn_udp4_output
Date: Fri, 19 Sep 2025 17:03:01 +0200 [thread overview]
Message-ID: <aM1wpYP5LYhM3jcz@krikkit> (raw)
In-Reply-To: <cd8193c9-1af8-4182-8e6a-a769acfde340@yahoo.com>
2025-09-18, 18:29:08 +0200, Marek Mietus wrote:
> W dniu 9/16/25 o 12:49, Sabrina Dubroca pisze:
> > 2025-09-12, 13:24:20 +0200, Marek Mietus wrote:
> > Why are you changing only ipv4? Is there something in the ipv6 code
> > that prevents this?
> >
>
> I'm not sure. I'm not as acquainted with IPv6 as I am with IPv4. (and thought I'd hold off
> until I got a positive response about the series)
Ok, understood.
> IPv4 already has some noref xmit optimizations, so it just felt like the right place to start.
There's also some in IPv6, see d14730b8e911 ("ipv6: use RCU in inet6_csk_xmit()").
--
Sabrina
prev parent reply other threads:[~2025-09-19 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250912112420.4394-1-mmietus97.ref@yahoo.com>
2025-09-12 11:24 ` [PATCH net-next v2 0/3] net: tunnel: introduce noref xmit flows for tunnels Marek Mietus
2025-09-12 11:24 ` [PATCH net-next v2 1/3] net: dst_cache: implement RCU variants for dst_cache helpers Marek Mietus
2025-09-16 9:28 ` Paolo Abeni
2025-09-12 11:24 ` [PATCH net-next v2 2/3] net: tunnel: implement noref flows in udp_tunnel_xmit_skb Marek Mietus
2025-09-12 11:24 ` [PATCH net-next v2 3/3] net: ovpn: use new noref xmit flow in ovpn_udp4_output Marek Mietus
2025-09-16 10:49 ` Sabrina Dubroca
2025-09-18 16:29 ` Marek Mietus
2025-09-19 15:03 ` Sabrina Dubroca [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=aM1wpYP5LYhM3jcz@krikkit \
--to=sd@queasysnail.net \
--cc=antonio@openvpn.net \
--cc=kuba@kernel.org \
--cc=mmietus97@yahoo.com \
--cc=netdev@vger.kernel.org \
--cc=openvpn-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).