Hi,
> > Shally - enque in order-of-completion or in-order-submission? What does
> > this mean in-
> > context of ipsec?
> > In general, there is bit of confusion when we are using terms async in ODP
> > context here.
> > It imply that queue is used to output events. an async implementation can
: Re: [lng-odp] [API-NEXT] API: IPSEC: Updating ipsec APIs to support
sNIC implementation.
Hi Nikhil,
Let me see if I understand the limitations:
Inbound IPsec processing - pkt/status destination may be:
For lookaside async mode
- SA queue: OK for pkts, OK for status
- pktio queue: not
-Original Message-
From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of Verma,
Shally
Sent: Friday, April 07, 2017 4:45 PM
To: Nikhil Agarwal ; lng-odp@lists.linaro.org
Subject: Re: [lng-odp] [API-NEXT] API: IPSEC: Updating ipsec APIs to support
sNIC implementation
lly wrote:
>
>
> -Original Message-
> From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of Nikhil
> Agarwal
> Sent: 07 April 2017 15:30
> To: lng-odp@lists.linaro.org
> Subject: [lng-odp] [API-NEXT] API: IPSEC: Updating ipsec APIs to support sNIC
&
-Original Message-
From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of Nikhil
Agarwal
Sent: 07 April 2017 15:30
To: lng-odp@lists.linaro.org
Subject: [lng-odp] [API-NEXT] API: IPSEC: Updating ipsec APIs to support sNIC
implementation.
Signed-off-by: Nikhil Agarwal
On 07.04.2017 13:00, Nikhil Agarwal wrote:
> +typedef union odp_ipsec_protocols_t {
> + /** Cipher algorithms */
> + struct {
> + /** ODP_IPSEC_ESP */
> + uint32_t esp: 1;
> +
> + /** ODP_IPSEC_AH */
> + uint32_t ah : 1;
Smal
Signed-off-by: Nikhil Agarwal
---
include/odp/api/spec/ipsec.h | 62 +++-
1 file changed, 26 insertions(+), 36 deletions(-)
diff --git a/include/odp/api/spec/ipsec.h b/include/odp/api/spec/ipsec.h
index b3dc0ca..d39e65d 100644
--- a/include/odp/api/spec/ip
