[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DB7PR04MB42526C939B48081D8981D11C8B7C0@DB7PR04MB4252.eurprd04.prod.outlook.com>
Date: Tue, 19 Feb 2019 10:20:17 +0000
From: Vakul Garg <vakul.garg@....com>
To: David Miller <davem@...emloft.net>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"borisp@...lanox.com" <borisp@...lanox.com>,
"aviadye@...lanox.com" <aviadye@...lanox.com>,
"davejwatson@...com" <davejwatson@...com>,
"doronrk@...com" <doronrk@...com>
Subject: RE: [PATCH net-next] net/tls: Move protocol constants from cipher
context to tls context
> -----Original Message-----
> From: David Miller <davem@...emloft.net>
> Sent: Sunday, February 17, 2019 7:45 AM
> To: Vakul Garg <vakul.garg@....com>
> Cc: netdev@...r.kernel.org; borisp@...lanox.com;
> aviadye@...lanox.com; davejwatson@...com; doronrk@...com
> Subject: Re: [PATCH net-next] net/tls: Move protocol constants from cipher
> context to tls context
>
> From: Vakul Garg <vakul.garg@....com>
> Date: Thu, 14 Feb 2019 07:11:35 +0000
>
> > Each tls context maintains two cipher contexts (one each for tx and rx
> > directions). For each tls session, the constants such as protocol
> > version, ciphersuite, iv size, associated data size etc are same for
> > both the directions and need to be stored only once per tls context.
> > Hence these are moved from 'struct cipher_context' to 'struct
> > tls_prot_info' and stored only once in 'struct tls_context'.
> >
> > Signed-off-by: Vakul Garg <vakul.garg@....com>
>
> Applied.
This has not yet made its way in git.
Can you please check?
Powered by blists - more mailing lists