Hi Akhil, I have started reviewing it. You can expect some feedback in the weekend.
Regards Abhinandan > -----Original Message----- > From: Akhil Goyal <gak...@marvell.com> > Sent: Thursday, September 22, 2022 12:02 AM > To: Volodymyr Fialko <vfia...@marvell.com>; dev@dpdk.org; Jerin Jacob > Kollanukkaran <jer...@marvell.com>; Gujjar, Abhinandan S > <abhinandan.guj...@intel.com>; Pavan Nikhilesh Bhagavatula > <pbhagavat...@marvell.com>; Shijith Thotton <sthot...@marvell.com>; > Hemant Agrawal <hemant.agra...@nxp.com>; Sachin Saxena > <sachin.sax...@oss.nxp.com>; Jayatheerthan, Jay > <jay.jayatheert...@intel.com> > Cc: Anoob Joseph <ano...@marvell.com>; Volodymyr Fialko > <vfia...@marvell.com> > Subject: RE: [PATCH 1/3] eventdev: introduce event cryptodev vector type > > Hi Abhinandan/Hemant, > > Can you review this patchset? > The library changes need to merged in RC1. > If no comments, this will be merged in couple of days. It has been over 6 > weeks > for this patch. > > Regards, > Akhil > > Subject: [PATCH 1/3] eventdev: introduce event cryptodev vector type > > > > Introduce ability to aggregate crypto operations processed by event > > crypto adapter into single event containing rte_event_vector whose > > event type is RTE_EVENT_TYPE_CRYPTODEV_VECTOR. > > > > Application should set RTE_EVENT_CRYPTO_ADAPTER_EVENT_VECTOR in > > rte_event_crypto_adapter_queue_conf::flag and provide vector > > configuration with respect of rte_event_crypto_adapter_vector_limits, > > which could be obtained by calling > > rte_event_crypto_adapter_vector_limits_get, to enable vectorization. > > > > The event crypto adapter would be responsible for vectorizing the > > crypto operations based on provided response information in > > rte_event_crypto_metadata::response_info. > > > > Updated drivers and tests accordingly to new API. > > > > Signed-off-by: Volodymyr Fialko <vfia...@marvell.com>
