On 4/22/2016 6:45 PM, Kim Phillips wrote:
> On Thu, 21 Apr 2016 13:31:47 +
> Horia Ioan Geanta Neag wrote:
>
>> On 4/20/2016 3:04 PM, Christophe Leroy wrote:
>>> What's the best way to implement the selection of the proper descriptor
>>> type ?
>>> * We can duplicate the templates but it mean
On Thu, 21 Apr 2016 13:31:47 +
Horia Ioan Geanta Neag wrote:
> On 4/20/2016 3:04 PM, Christophe Leroy wrote:
> > What's the best way to implement the selection of the proper descriptor
> > type ?
> > * We can duplicate the templates but it means that when both types are
> > supported the driv
On Thu, 21 Apr 2016 13:31:47 +
Horia Ioan Geanta Neag wrote:
> On 4/20/2016 3:04 PM, Christophe Leroy wrote:
> > Today, in Talitos driver crypto alg registration is based on predefined
> > templates with a predefined descriptor type and verification against the
> > descriptors supported by th
On 4/20/2016 3:04 PM, Christophe Leroy wrote:
> Today, in Talitos driver crypto alg registration is based on predefined
> templates with a predefined descriptor type and verification against the
> descriptors supported by the HW. This works well for ALG that require a
> unique descriptor. But fo
Today, in Talitos driver crypto alg registration is based on predefined
templates with a predefined descriptor type and verification against the
descriptors supported by the HW. This works well for ALG that require a
unique descriptor. But for IPsec this is slightly different:
* IPsec can be per
