> -Original Message-
> From: Bill Fischofer [mailto:bill.fischo...@linaro.org]
> Sent: Friday, June 09, 2017 6:27 PM
> To: Savolainen, Petri (Nokia - FI/Espoo)
> Cc: Dmitry Eremin-Solenikov ; lng-
> o...@lists.linaro.org
> Subject: Re: [lng-odp] [API-NEXT PATCH 0/
o...@lists.linaro.org
>> Subject: Re: [lng-odp] [API-NEXT PATCH 0/2] IPSEC packet event
>>
>> Petri,
>>
>> On 09.06.2017 13:51, Petri Savolainen wrote:
>> > Requires "[API-NEXT PATCH v2 0/2] IPsec API update".
>> >
>> > Input and outp
> -Original Message-
> From: Dmitry Eremin-Solenikov [mailto:dmitry.ereminsoleni...@linaro.org]
> Sent: Friday, June 09, 2017 2:49 PM
> To: Petri Savolainen ; lng-
> o...@lists.linaro.org
> Subject: Re: [lng-odp] [API-NEXT PATCH 0/2] IPSEC packet event
>
> Petr
Petri,
On 09.06.2017 13:51, Petri Savolainen wrote:
> Requires "[API-NEXT PATCH v2 0/2] IPsec API update".
>
> Input and output of IPSEC operations are packets. Parameter and
> result structures are cleaner when packet arrays are direct
> parameters to functions. Also API is more flexible for
>
Requires "[API-NEXT PATCH v2 0/2] IPsec API update".
Input and output of IPSEC operations are packets. Parameter and
result structures are cleaner when packet arrays are direct
parameters to functions. Also API is more flexible for
application or API pipelining when output is packets with
additio