On Tue, Jun 27, 2017 at 2:51 PM, Savolainen, Petri (Nokia - FI/Espoo)
<petri.savolai...@nokia.com> wrote:
>> > diff --git a/platform/linux-generic/include/odp/api/plat/event_types.h
>> b/platform/linux-generic/include/odp/api/plat/event_types.h
>> > index 0f51783..adf2c31 100644
>> > --- a/platform/linux-generic/include/odp/api/plat/event_types.h
>> > +++ b/platform/linux-generic/include/odp/api/plat/event_types.h
>> > @@ -4,7 +4,6 @@
>> > * SPDX-License-Identifier: BSD-3-Clause
>> > */
>> >
>> > -
>> > /**
>> > * @file
>> > *
>> > @@ -39,7 +38,9 @@ typedef enum odp_event_type_t {
>> > ODP_EVENT_PACKET = 2,
>> > ODP_EVENT_TIMEOUT = 3,
>> > ODP_EVENT_CRYPTO_COMPL = 4,
>> > - ODP_EVENT_IPSEC_RESULT = 5
>> > + ODP_EVENT_IPSEC_RESULT = 5,
>> > + ODP_EVENT_COMP_COMPL = 6,
>> > + ODP_EVENT_DECOMP_COMPL = 7
>> > } odp_event_type_t;
>
> Event subtypes are now in api-next. This needs to be rebased on top of that.
> Part of the rebase is definition of results as ODP_EVENT_PACKET type +
> ODP_EVENT_PACKET_COMP subtype (not as COMP_COMPL events). Only one subtype
> for comp, the same way as IPsec has ODP_EVENT_PACKET_IPSEC subtype which is
> for both in- and outbound IPsec. It would be preferable to align comp API to
> IPsec API also in other parts.
So you mean if application has both compression and decompression
ongoing simultaneously, onus is on application to track whether event
is from compress_enq() or decomp_enq() call ?
Shally
>
> -Petri
