From: Antonio Quartulli <antonio@openvpn.net>
To: Neal Cardwell <ncardwell@google.com>
Cc: netdev@vger.kernel.org, Marco Baffo <marco@mandelbit.com>,
Sabrina Dubroca <sd@queasysnail.net>,
Ralf Lici <ralf@mandelbit.com>, Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next 4/7] selftests: ovpn: enable TCP_NODELAY on TCP sockets
Date: Fri, 9 Oct 2026 14:29:12 +0200 [thread overview]
Message-ID: <fd4fc9f9-3b8d-4a5b-b308-96969c8c9de8@openvpn.net> (raw)
In-Reply-To: <CADVnQymvjmpFE95MFDLwHJJpusZ+FfnHyLs4+bo80GjtrLhafQ@mail.gmail.com>
Hi,
On 08/10/2026 15:59, Neal Cardwell wrote:
> On Wed, Oct 7, 2026 at 9:38 AM Antonio Quartulli <antonio@openvpn.net> wrote:
>>
>> From: Marco Baffo <marco@mandelbit.com>
>>
>> Userspace now enables TCP_NODELAY by default. Enable it for
>> ovpn-cli's TCP sockets too.
>
> This claim is accurate in context, but terse. I would suggest a more
> precise wording, like: “Since OpenVPN 2.7.6, openvpn unconditionally
> sets TCP_NODELAY on its TCP sockets. Do the same in ovpn-cli so the
> TCP selftests match that configuration.”
ok! I'll make the wording more precise and explicit about the version
introducing this change in userspace.
>
> Sashiko’s suggestion to keep an option for running with Nagle on seems
> worthwhile. Peers on 2.7.0–2.7.5, and mixed-version setups, will keep
> producing Nagle-on sockets under ovpn for a while. It might be nice to
> have test coverage to ensure those setups do not get broken by kernel
> changes.
>
True, extending the tests to cover both case shouldn't be a big deal.
Will respin with both points addressed.
Regards,
--
Antonio Quartulli
OpenVPN Inc.
next prev parent reply other threads:[~2026-10-09 12:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 13:30 [PATCH net-next 0/7] pull request: ovpn 2026-10-07 Antonio Quartulli
2026-10-07 13:30 ` [PATCH net-next 1/7] ovpn: Fix the return value in ovpn_bind_from_sockaddr() kernel-doc Antonio Quartulli
2026-10-07 13:30 ` [PATCH net-next 2/7] ovpn: remove unused work field from struct ovpn_socket Antonio Quartulli
2026-10-07 13:30 ` [PATCH net-next 3/7] ovpn: remove redundant peer NULL checks in crypto post functions Antonio Quartulli
2026-10-07 13:30 ` [PATCH net-next 4/7] selftests: ovpn: enable TCP_NODELAY on TCP sockets Antonio Quartulli
2026-10-08 13:32 ` netdev-bot+sashiko
2026-10-08 13:59 ` Neal Cardwell
2026-10-09 12:29 ` Antonio Quartulli [this message]
2026-10-07 13:30 ` [PATCH net-next 5/7] selftests: ovpn: wait for the TCP server key setup before traffic Antonio Quartulli
2026-10-08 13:32 ` netdev-bot+sashiko
2026-10-07 13:30 ` [PATCH net-next 6/7] ovpn: send peer object along with PEER_DEL_NTF Antonio Quartulli
2026-10-08 13:32 ` netdev-bot+sashiko
2026-10-07 13:30 ` [PATCH net-next 7/7] MAINTAINERS: ovpn: add Ralf Lici as reviewer Antonio Quartulli
-- strict thread matches above, loose matches on Subject: below --
2026-09-30 22:25 [PATCH net-next 0/7] pull request: ovpn 2026-09-30 Antonio Quartulli
2026-09-30 22:25 ` [PATCH net-next 4/7] selftests: ovpn: enable TCP_NODELAY on TCP sockets Antonio Quartulli
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=fd4fc9f9-3b8d-4a5b-b308-96969c8c9de8@openvpn.net \
--to=antonio@openvpn.net \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=marco@mandelbit.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ralf@mandelbit.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