> -----Original Message-----
> From: dev [mailto:[email protected]] On Behalf Of De Lara Guarch, Pablo
> Sent: Tuesday, July 10, 2018 6:21 PM
> To: Anoob Joseph <[email protected]>; Doherty, Declan
> <[email protected]>
> Cc: Akhil Goyal <[email protected]>; Ankur Dwivedi
> <[email protected]>; Jerin Jacob
> <[email protected]>; Narayana Prasad
> <[email protected]>; [email protected]
> Subject: Re: [dpdk-dev] [PATCH v2 0/4] add head/tailroom requirement for
> crypto PMDs
>
>
>
> > -----Original Message-----
> > From: Anoob Joseph [mailto:[email protected]]
> > Sent: Tuesday, July 10, 2018 3:43 PM
> > To: Doherty, Declan <[email protected]>; De Lara Guarch, Pablo
> > <[email protected]>
> > Cc: Anoob Joseph <[email protected]>; Akhil Goyal
> > <[email protected]>; Ankur Dwivedi
> > <[email protected]>; Jerin Jacob
> > <[email protected]>; Narayana Prasad
> > <[email protected]>; [email protected]
> > Subject: [PATCH v2 0/4] add head/tailroom requirement for crypto PMDs
> >
> > This series adds the ability, for crypto PMDs, to communicate the
> > minimum head/tailroom requirement it may have, using the existing
> > cryptodev_info framework.
> >
> > The availability and use of head/tailroom is an optimisation if the
> > hardware supports its use for crypto-op info. Devices that do not
> > support using the head/tailroom, can continue to operate without any
> performance-drop.
> >
> > Cavium's OcteonTX crypto hardware supports this feature and would use
> > headroom and tailroom for submitting crypto-ops to the hardware.
> >
>
> Series-acked-by: Pablo de Lara <[email protected]>
Series applied to dpdk-next-crypto.
Thanks,
Pablo
