From: Dmitry Eremin-Solenikov <[email protected]> For INLINE-destined SAs it is typical to have packets processed through INLINE API. So, let's invert the inline_mode flag to mean that the packet was processed through ASYNC API.
Signed-off-by: Dmitry Eremin-Solenikov <[email protected]> --- /** Email created from pull request 22 (lumag:ipsec-limits) ** https://github.com/Linaro/odp/pull/22 ** Patch: https://github.com/Linaro/odp/pull/22.patch ** Base sha: 3ea9c1dac34e0fb4785b0d643056c731daa55e85 ** Merge commit sha: 85b927011c941f816b853da7284c0c3a939c5efb **/ include/odp/api/spec/ipsec.h | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/include/odp/api/spec/ipsec.h b/include/odp/api/spec/ipsec.h index 3a33845..c16fcf1 100644 --- a/include/odp/api/spec/ipsec.h +++ b/include/odp/api/spec/ipsec.h @@ -901,8 +901,11 @@ typedef union odp_ipsec_op_status_t { union { /** Status flags */ struct { - /** Packet was processed in inline mode */ - uint32_t inline_mode : 1; + /** + * Packet was processed in ASYNC mode through + * the SA configured for INLINE mode. + */ + uint32_t non_inline_mode : 1; } flag;
