>> > >> > + @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 https://urldefense.proofpoint.com/v2/url?u=http- >3A__dpdk.org_git_next_dpdk-2Dnext- >2Deventdev&d=DwIGaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=G9w4KsPaQLACBfGCL >35PtiRH996yqJDxAZwrWegU2qQ&m=-yaLm_cvg5cKTbBy3OoUs719W- >E3ARETajJQmUvoE4aSAPjcEn1kulkRNxTn841D&s=lZjsn2zecck8IBBQRA7fId7BXSYKk >U8Tjj10gNQLB6U&e= >> > > * Apply [v5] app/eventdev: add crypto producer mode >> > > git-pw --server https://urldefense.proofpoint.com/v2/url?u=https- >3A__patches.dpdk.org_api_1.2_&d=DwIGaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=G >9w4KsPaQLACBfGCL35PtiRH996yqJDxAZwrWegU2qQ&m=- >yaLm_cvg5cKTbBy3OoUs719W- >E3ARETajJQmUvoE4aSAPjcEn1kulkRNxTn841D&s=VBQtpQ8vwHt9BnMrPLzSneOm >zhLdP5bfyLuY42fCnak&e= --project dpdk >> > > patch apply 107645 >> > > * Apply [RFC] app/eventdev: add software crypto adapter support >> > > git-pw --server https://urldefense.proofpoint.com/v2/url?u=https- >3A__patches.dpdk.org_api_1.2_&d=DwIGaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=G >9w4KsPaQLACBfGCL35PtiRH996yqJDxAZwrWegU2qQ&m=- >yaLm_cvg5cKTbBy3OoUs719W- >E3ARETajJQmUvoE4aSAPjcEn1kulkRNxTn841D&s=VBQtpQ8vwHt9BnMrPLzSneOm >zhLdP5bfyLuY42fCnak&e= --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? >
Looks like an issue in crypto adapter service. The service is starting with OP_FORWARD, if RTE_EVENT_DEV_CAP_IMPLICIT_RELEASE_DISABLE is set. Abhinandan can confirm.
