> -----Original Message-----
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Akhil Goyal
> Sent: Monday, June 18, 2018 7:30 AM
> To: De Lara Guarch, Pablo <pablo.de.lara.gua...@intel.com>; Doherty, Declan
> <declan.dohe...@intel.com>; akhil.go...@nxp.com; ravi1.ku...@amd.com;
> jerin.ja...@caviumnetworks.com; Zhang, Roy Fan <roy.fan.zh...@intel.com>;
> Trahe, Fiona <fiona.tr...@intel.com>; t...@semihalf.com;
> jianjay.z...@huawei.com
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 6/6] cryptodev: replace mbuf scatter gather 
> flag
> 
> Hi Pablo,
> On 6/9/2018 3:32 AM, Pablo de Lara wrote:
> > The current mbuf scatter gatter feature flag is too ambiguous, as it
> > is not clear if input and/or output buffers can be scatter gather
> > mbufs or not.
> >
> > Therefore, two new flags will replace this flag:
> > RTE_CRYPTODEV_FF_MBUF_SCATTER_GATHER_IN and
> > RTE_CRYPTODEV_FF_MBUF_SCATTER_GATHER_OUT.
> >
> There may be a case, SG supported in input buffer and we use in-place
> processing and driver may support that but may not support SG for out buffers 
> in
> case of OOP. How can we handle this type of case?

Agree. I will send a new version with more flags, so we can cover all scenarios.

Thanks for the feedback!
Pablo

Reply via email to