From: Atul Gupta <atul.gupta@chelsio.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
linux-crypto@vger.kernel.org, netdev@vger.kernel.org,
dt@chelsio.com
Subject: Re: [crypto 0/4] Inline TLS client and v6 support
Date: Wed, 10 Apr 2019 10:56:37 +0530 [thread overview]
Message-ID: <a443baa3-a192-2d3d-d3bf-20b0f12e53a4@chelsio.com> (raw)
In-Reply-To: <20190409110137.1ff359e0@cakuba.netronome.com>
On 4/9/2019 11:31 PM, Jakub Kicinski wrote:
> On Tue, 9 Apr 2019 08:22:34 -0700, Atul Gupta wrote:
>> Extends Inline TLS record processing to TLS client. connect
>> API is added to tls_context to setup hardware for TLS
>> connection and handshake. Functionality wise, this makes the solution
>> end-to-end Inline TLS capable. TLS server and client
>> can operate in Inline mode and leverage hardware for complete
>> TLS record offload.
>> [0004] Adds the IPv6 support for Inline TLS server/client.
>>
>> RFC series for this patch was created against net-next and
>> submitted on 18 Jan'2019.
>> This series is created against Herbert branch.
> Sorry if someone already asked this, but is your HW doing full ToE
> for all this TLS "record offload" stuff?
Yes Jakub
Thanks
next prev parent reply other threads:[~2019-04-10 5:27 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 [this message]
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
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=a443baa3-a192-2d3d-d3bf-20b0f12e53a4@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