Hi Akhil, > -----Original Message----- > From: Akhil Goyal <akhil.go...@nxp.com> > Sent: Sunday, May 10, 2020 12:12 AM > To: dev@dpdk.org > Cc: ruifeng.w...@arm.com; Doherty, Declan <declan.dohe...@intel.com>; > asoma...@amd.com; ano...@marvell.com; Zhang, Roy Fan > <roy.fan.zh...@intel.com>; Trahe, Fiona <fiona.tr...@intel.com>; > rnagadhee...@marvell.com; adwiv...@marvell.com; g.si...@nxp.com; > hemant.agra...@nxp.com; jianjay.z...@huawei.com; De Lara Guarch, Pablo > <pablo.de.lara.gua...@intel.com>; Dybkowski, AdamX > <adamx.dybkow...@intel.com>; apeksha.gu...@nxp.com; Akhil Goyal > <akhil.go...@nxp.com> > Subject: [PATCH v2 1/9] cryptodev: add feature flag for non-byte aligned data > > Some wireless algos like SNOW, ZUC may support input data in bits which are > not byte aligned. However, not all PMDs can support this requirement. Hence > added a new feature flag RTE_CRYPTODEV_FF_NON_BYTE_ALIGNED_DATA > to identify which all PMDs can support non-byte aligned data. > > Signed-off-by: Akhil Goyal <akhil.go...@nxp.com> > Acked-by: Fiona Trahe <fiona.tr...@intel.com>
On these PMDs, some of these algorithms do not support non byte aligned data. For instance, for ZUC, the cipher algorithm doesn't support length in bits, but the authentication algorithm does. All test pass because in the tests we are doing encryption in bytes and then we mask off the bits not used. Wonder if we need two different flags for this, one for cipher and another one for authentication. Maybe again this is not enough, since we should have a flag per algorithm... and starting with this flag is a step forward. What do you think? Thanks for looking into this! Pablo
