On Wed, Apr 14, 2021 at 12:36 PM Gujjar, Abhinandan S <abhinandan.guj...@intel.com> wrote: > > > > > -----Original Message----- > > From: Shijith Thotton <shijith.thot...@gmail.com> > > Sent: Tuesday, April 13, 2021 1:21 PM > > To: Gujjar, Abhinandan S <abhinandan.guj...@intel.com> > > Cc: Shijith Thotton <sthot...@marvell.com>; dev@dpdk.org; Jerin Jacob > > <jer...@marvell.com>; Akhil Goyal <gak...@marvell.com>; Anoob Joseph > > <ano...@marvell.com> > > Subject: Re: [dpdk-dev] [PATCH v2] eventdev: fix case to initiate crypto > > adapter service
> > > > As per comments above, below checks are used to initiate SW service if: > > 1. PMDs supports OP_NEW, but not OP_FWD, in FWD mode. > > 2. Does not support OP_NEW and OP_FWD. > > > > I have fixed the first point where only support for OP_NEW is checked in > > forward mode, by adding a check for no OP_FWD capability. > Sounds good. > > Acked-by: abhinandan.guj...@intel.com Applied to dpdk-next-eventdev/for-main. Thanks. > > > > > > > adapter->mode == > > > > RTE_EVENT_CRYPTO_ADAPTER_OP_FORWARD) || > > > > (!(cap & > > > > RTE_EVENT_CRYPTO_ADAPTER_CAP_INTERNAL_PORT_OP_NEW) && > > > > !(cap & > > > > RTE_EVENT_CRYPTO_ADAPTER_CAP_INTERNAL_PORT_OP_FWD) && > > > > -- > > > > 2.25.1 > > >
