On Thu, 11 Apr 2019 09:47:09 +0530, Atul Gupta wrote: > On 4/10/2019 9:28 PM, Jakub Kicinski wrote: > > On Wed, 10 Apr 2019 10:56:37 +0530, Atul Gupta wrote: > >> 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 > > So from what I grok you already feed all the data directly to the > > socket completely bypassing the lower layers of the networking stack, > > and with this patch set you'd also move 3WHS into the FW? > Yes, that's correct. I believe then it's a no-go from netdev perspective.
