Applies on top of: "[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
additional metadata. Application or API pipeline stages which
do not care about IPSEC results may work on basic packet metadata.
v3:
* typo corrected (Bill)
v2:
* Introduce event subtype
* event type "packet" is the same for all packets
* event subtype "packet_ipsec" indicates that a packet contain IPSEC results
* Added output packet format description, which was accidentally left out
from previous version (moved text from deleted result type to
odp_ipsec_in() / odp_ipsec_out() documentation)
Petri Savolainen (3):
api: event: add subtype to expand event type
api: ipsec: change IPSEC result to packet
api: ipsec: disable event is the last event
include/odp/api/spec/event.h | 80 +++-
include/odp/api/spec/ipsec.h | 417 ++++++++++++---------
include/odp/arch/default/api/abi/event.h | 9 +-
.../include/odp/api/plat/event_types.h | 8 +-
platform/linux-generic/odp_ipsec.c | 67 +++-
5 files changed, 372 insertions(+), 209 deletions(-)
--
2.13.0
