[PATCH v5] app/eventdev: add crypto producer mode

[Van Haaren, Harry]

<snip>

> > -----Original Message-----
> > From: Jerin Jacob <jerinjacobk at gmail.com>
> > Sent: Wednesday, February 16, 2022 2:25 PM
> > To: Gujjar, Abhinandan S <abhinandan.gujjar at intel.com>; Hemant Agrawal
> > <hemant.agrawal at nxp.com>; Nipun Gupta <nipun.gupta at nxp.com>; Van
> > Haaren, Harry <harry.van.haaren at intel.com>
> > Cc: Shijith Thotton <sthotton at marvell.com>; Jerin Jacob Kollanukkaran
> > <jerinj at marvell.com>; dev at dpdk.org
> > Subject: Re: [PATCH v5] app/eventdev: add crypto producer mode
> >
> > + @Van Haaren, Harry

Hi All,

I have been away on vacation for the last week - hence the delay in reply on this thread.

<snip discussion>

> > > [1]
> > > Steps to reproduce:
> > > * Clone http://dpdk.org/git/next/dpdk-next-eventdev
> > > * Apply [v5] app/eventdev: add crypto producer mode
> > >   git-pw --server https://patches.dpdk.org/api/1.2/ --project dpdk
> > > patch apply 107645
> > > * Apply [RFC] app/eventdev: add software crypto adapter support
> > >   git-pw --server https://patches.dpdk.org/api/1.2/ --project dpdk
> > > patch apply 107029
> > > * meson x86_build_debug  -Dc_args='-g -O0' -Ddisable_drivers="*/cnxk"
> > > * ninja -C x86_build_debug
> > > * Command to reproduce crash
> > >   sudo ./x86_build_debug/app/dpdk-test-eventdev -l 0-8 -s 0xf0
> > > --vdev=event_sw0  --vdev="crypto_null" -- --prod_type_cryptodev
> > > --crypto_adptr_mode 0 --test=perf_queue --stlist=a --wlcores 1
> > > --plcores 2

Can confirm that these steps indeed cause segfault as reported.

In debugging, it seems like there are *zero* NEW events, and large numbers of
RELEASE events are enqueued... if so, this is not compliant to the Eventdev API.
Can somebody confirm that?

The SW PMD is being told there are events to release, but there aren't any.
Eventually, this leads to a mismatch in credit allocations, which then causes
the IQ-chunks datastructure to corrupt.

All in all, I'm not convinced this is a SW PMD issue yet - initial testing
points to incorrect event OP NEW/FWD/RELEASE usage. Can we verify
that the OPs being sent are correct?

Regards, -Harry