Re: [dpdk-dev] [PATCH] compressdev: add feature flag to specify where processing is done

[Shally Verma <shallyv@marvell.com>]

>-----Original Message-----
>From: Trahe, Fiona <fiona.trahe@intel.com>
>Sent: 16 January 2019 18:15
>To: Shally Verma <shallyv@marvell.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Verma, Shally
><Shally.Verma@cavium.com>; Stephen Hemminger <stephen@networkplumber.org>
>Cc: dev@dpdk.org; akhil.goyal@nxp.com; Jozwiak, TomaszX <tomaszx.jozwiak@intel.com>; Gupta, Ashish
><Ashish.Gupta@cavium.com>; Daly, Lee <lee.daly@intel.com>; Luse, Paul E <paul.e.luse@intel.com>; Anoob Joseph
><anoobj@marvell.com>; Tejasree Kondoj <ktejasree@marvell.com>; Trahe, Fiona <fiona.trahe@intel.com>
>Subject: RE: [dpdk-dev] [PATCH] compressdev: add feature flag to specify where processing is done
>
>Hi Shally,
>
>> So, would like to understand it bit more on how flag would help app to tune itself as per current given
>> description?
>> For example, if PMD says, It does actual processing in dequeue, then how it will impact app design for
>> better performance?
>[Fiona] One example: It could enqueue a large burst, say 32 ops. Then if it tried to dequeue 32 ops that
>could be a very long blocking call. So instead it could choose to dequeue 8 at a time.
>Vice versa if work done in enqueue.
Ok. I get it. For now I would suggest to keep it as per original description i.e.  Read only capability flag which app can read tune itself. This will help current octeontx compression PMD as well. We will revisit on its description based on requirement.

Thanks
Shally