RE: [RFC crypto v3 8/9] chtls: Register the ULP

2018-02-08 Thread Vakul Garg
ry...@vger.kernel.org; ganes...@chelsio.co; netdev@vger.kernel.org; > da...@davemloft.net; Boris Pismenny ; Ilya > Lesokhin > Subject: RE: [RFC crypto v3 8/9] chtls: Register the ULP > > I thought about this and approach below can avoid new ulp type: > > 1. Register Inline TL

RE: [RFC crypto v3 8/9] chtls: Register the ULP

2018-02-08 Thread Atul Gupta
2018 10:14 PM To: Atul Gupta Cc: s...@queasysnail.net; herb...@gondor.apana.org.au; linux-cry...@vger.kernel.org; ganes...@chelsio.co; netdev@vger.kernel.org; da...@davemloft.net; Boris Pismenny ; Ilya Lesokhin Subject: Re: [RFC crypto v3 8/9] chtls: Register the ULP On 01/31/18 04:14 PM, Atu

RE: [RFC crypto v3 8/9] chtls: Register the ULP

2018-01-31 Thread Atul Gupta
Pismenny ; Ilya Lesokhin Subject: Re: [RFC crypto v3 8/9] chtls: Register the ULP On 01/31/18 04:14 PM, Atul Gupta wrote: > > > On Tuesday 30 January 2018 10:41 PM, Dave Watson wrote: > > On 01/30/18 06:51 AM, Atul Gupta wrote: > > > > > What I was referring is

Re: [RFC crypto v3 8/9] chtls: Register the ULP

2018-01-31 Thread Dave Watson
On 01/31/18 04:14 PM, Atul Gupta wrote: > > > On Tuesday 30 January 2018 10:41 PM, Dave Watson wrote: > > On 01/30/18 06:51 AM, Atul Gupta wrote: > > > > > What I was referring is that passing "tls" ulp type in setsockopt > > > may be insufficient to make the decision when multi HW assist Inline

Re: [RFC crypto v3 8/9] chtls: Register the ULP

2018-01-31 Thread Atul Gupta
On Tuesday 30 January 2018 10:41 PM, Dave Watson wrote: On 01/30/18 06:51 AM, Atul Gupta wrote: What I was referring is that passing "tls" ulp type in setsockopt may be insufficient to make the decision when multi HW assist Inline TLS solution exists. Setting the ULP doesn't choose HW or SW

Re: [RFC crypto v3 8/9] chtls: Register the ULP

2018-01-30 Thread Dave Watson
On 01/30/18 06:51 AM, Atul Gupta wrote: > What I was referring is that passing "tls" ulp type in setsockopt > may be insufficient to make the decision when multi HW assist Inline > TLS solution exists. Setting the ULP doesn't choose HW or SW implementation, I think that should be done later when

RE: [RFC crypto v3 8/9] chtls: Register the ULP

2018-01-29 Thread Atul Gupta
al Message- From: Atul Gupta Sent: Sunday, January 28, 2018 11:26 AM To: 'Dave Watson' Cc: herb...@gondor.apana.org.au; linux-cry...@vger.kernel.org; ganes...@chelsio.co; netdev@vger.kernel.org; da...@davemloft.net; Boris Pismenny ; Ilya Lesokhin Subject: RE: [RFC crypto v3 8/9] cht

RE: [RFC crypto v3 8/9] chtls: Register the ULP

2018-01-27 Thread Atul Gupta
Subject: Re: [RFC crypto v3 8/9] chtls: Register the ULP <1513769897-26945-1-git-send-email-atul.gu...@chelsio.com> On 12/20/17 05:08 PM, Atul Gupta wrote: > +static void __init chtls_init_ulp_ops(void) { > + chtls_base_prot = tcp_prot; > + chtls

Re: [RFC crypto v3 8/9] chtls: Register the ULP

2018-01-25 Thread Dave Watson
<1513769897-26945-1-git-send-email-atul.gu...@chelsio.com> On 12/20/17 05:08 PM, Atul Gupta wrote: > +static void __init chtls_init_ulp_ops(void) > +{ > + chtls_base_prot = tcp_prot; > + chtls_base_prot.hash= chtls_hash; > + chtls_base_prot.unhash =