From: Atul Gupta <atul.gupta@chelsio.com>
To: David Miller <davem@davemloft.net>, jakub.kicinski@netronome.com
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
netdev@vger.kernel.org, dt@chelsio.com
Subject: Re: [crypto 0/4] Inline TLS client and v6 support
Date: Mon, 15 Apr 2019 14:40:03 +0530 [thread overview]
Message-ID: <11ea3b48-4b50-3384-4e43-81248ec812b3@chelsio.com> (raw)
In-Reply-To: <20190411.115228.894374097382770159.davem@davemloft.net>
On 4/12/2019 12:22 AM, David Miller wrote:
> From: Jakub Kicinski <jakub.kicinski@netronome.com>
> Date: Thu, 11 Apr 2019 11:45:06 -0700
>
>> I think the "netdev community" feels pretty strongly about preventing
>> protocol ossification and bypassing crucial parts of the infrastructure.
> Correct.
I understand the concern, the objective of complete offload of TLS record is an option to kTLS and other solutions. Have taken care to keep code out of netdev into crypto driver and allow user to choose record offload capability. Application buffer from socket is posted to HW for encryption, Segmentation and Tx on wire. The path provides near line-rate [100Gbps] Inline encrypt/decrypt b/w. If community feels this path adds value and can sit in crypto driver then I will work on build comments and resend v1?
Regards
Atul
next prev parent reply other threads:[~2019-04-15 9:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 15:22 [crypto 0/4] Inline TLS client and v6 support Atul Gupta
2019-04-09 18:01 ` Jakub Kicinski
2019-04-10 5:26 ` Atul Gupta
2019-04-10 15:58 ` Jakub Kicinski
2019-04-11 4:17 ` Atul Gupta
2019-04-11 16:40 ` Jakub Kicinski
[not found] ` <ae56c100-d072-bf6b-465a-5136d29b84be@chelsio.com>
2019-04-11 18:45 ` Jakub Kicinski
2019-04-11 18:52 ` David Miller
2019-04-15 9:10 ` Atul Gupta [this message]
2019-04-15 9:36 ` Herbert Xu
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=11ea3b48-4b50-3384-4e43-81248ec812b3@chelsio.com \
--to=atul.gupta@chelsio.com \
--cc=davem@davemloft.net \
--cc=dt@chelsio.com \
--cc=herbert@gondor.apana.org.au \
--cc=jakub.kicinski@netronome.com \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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