From: Jakub Kicinski <kuba@kernel.org>
To: Maxim Mikityanskiy <maximmi@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Daniel Borkmann <daniel@iogearbox.net>,
Paolo Abeni <pabeni@redhat.com>,
Boris Pismenny <borisp@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>, Gal Pressman <gal@nvidia.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tls: Add opt-in zerocopy mode of sendfile()
Date: Tue, 3 May 2022 12:24:23 -0700 [thread overview]
Message-ID: <20220503122423.29f48b61@kernel.org> (raw)
In-Reply-To: <db461463-23ac-de03-806b-6ce2b7ea1d6b@nvidia.com>
On Tue, 3 May 2022 21:56:48 +0300 Maxim Mikityanskiy wrote:
> >> Yes, I agree that if the application opted in, it should work properly
> >> regardless of whether the optimization actually did turn on. However,
> >> the indication could be useful, for example, for diagnostic purposes, to
> >> show the user whether zerocopy mode was enabled, if someone is trying to
> >> debug some performance issue. If you insist, though, I can make
> >> setsockopt succeed and getsockopt return 1. What do you think?
> >
> > I'd say "whether the optimization is applicable" rather than "whether
> > the optimization is turned on". User can check whether the connection
> > is using SW or HW TLS if they want to make sure it's taken advantage of.
> >
> > Speaking of which, should we report the state of this knob via socket
> > diag?
>
> That sounds like an option, I'll take a look. TLS doesn't expose
> anything via diag yet, does it? The only option to distinguish SW/HW TLS
> is ethtool, and there is no per-socket check, right? Cause a HW TLS
> socket can downgrade to SW after tls_device_down, and ethtool won't show it.
It does - look for tls_get_info()
next prev parent reply other threads:[~2022-05-03 19:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 17:50 [PATCH net-next] tls: Add opt-in zerocopy mode of sendfile() Maxim Mikityanskiy
2022-04-28 22:11 ` Jakub Kicinski
2022-04-29 14:21 ` Maxim Mikityanskiy
2022-04-29 19:11 ` Jakub Kicinski
2022-05-03 18:56 ` Maxim Mikityanskiy
2022-05-03 19:24 ` Jakub Kicinski [this message]
2022-05-04 9:49 ` David Laight
2022-05-05 12:40 ` Maxim Mikityanskiy
2022-05-05 13:48 ` David Laight
2022-05-05 18:27 ` Maxim Mikityanskiy
2022-05-06 8:09 ` David Laight
2022-05-06 16:34 ` Maxim Mikityanskiy
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=20220503122423.29f48b61@kernel.org \
--to=kuba@kernel.org \
--cc=borisp@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=gal@nvidia.com \
--cc=maximmi@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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).