From: Shally Verma
An API set to add compression/decompression support in ODP
interface.
Signed-off-by: Shally Verma
Signed-off-by: Mahipal Challa
---
include/odp/api/spec/comp.h | 668
1 file changed, 668 insertions(+)
diff --git a/include/odp/a
Hi,
This proposal supports both sync and async compression offload in a single
API following the crypto model, IMO We can separate SYNC and ASYNC
compression offload as two different APIs and only add ASYNC compression
offload in the first version and if required we can add SYNC compression
mode a
...@lists.linaro.org] On Behalf Of Bala
Manoharan
Sent: Tuesday, March 21, 2017 4:18 PM
To: Mahipal Challa
Cc: prasad.athr...@cavium.com; faisal.mas...@cavium.com; Mahipal Challa
; mcha...@cavium.com; lng-odp-forward
Subject: Re: [lng-odp] [RFC, API-NEXT v1 1/1] comp:compression interface
Hi
Hi,
My understanding is that:
- compression can be used in stateless or statefull mode. How can we
differentiate between the two configurations: by specifying a special
algorithm on session creation or by setting "last" field to "true" for
every operation? Do we need this setting per operation or
: [lng-odp] [RFC, API-NEXT v1 1/1] comp:compression interface
Hi,
My understanding is that:
- compression can be used in stateless or statefull mode. How can we
differentiate between the two configurations: by specifying a special algorithm
on session creation or by setting "last" fiel
; Masood, Faisal
; Challa, Mahipal ;
lng-odp-forward ; Challa, Mahipal
Subject: Re: [lng-odp] [RFC, API-NEXT v1 1/1] comp:compression interface
Moreover, if both modes need to be added it is better to follow IPSEC APIs
approach instead of crypto APIs, where SYNC and ASYNC APIs are different and
