From: David Laight <David.Laight@ACULAB.COM>
To: 'Maxim Mikityanskiy' <maximmi@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>
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" <netdev@vger.kernel.org>
Subject: RE: [PATCH net-next] tls: Add opt-in zerocopy mode of sendfile()
Date: Wed, 4 May 2022 09:49:13 +0000 [thread overview]
Message-ID: <3f5f17a11d294781a5e500b3903aa902@AcuMS.aculab.com> (raw)
In-Reply-To: <db461463-23ac-de03-806b-6ce2b7ea1d6b@nvidia.com>
> > If you declare the union on the stack in the callers, and pass by value
> > - is the compiler not going to be clever enough to still DDRT?
>
> Ah, OK, it should do the thing. I thought you wanted me to ditch the
> union altogether.
Some architectures always pass struct/union by address.
Which is probably not what you had in mind.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-05-04 9:49 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
2022-05-04 9:49 ` David Laight [this message]
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=3f5f17a11d294781a5e500b3903aa902@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=borisp@nvidia.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--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).