On Sun, Jan 22, 2023 at 02:55:18PM +0100, David Marchand wrote: > On Wed, Jan 18, 2023 at 8:54 PM Tyler Retzlaff > <roret...@linux.microsoft.com> wrote: > > > > Replace the rte_thread_setname API which operates on pthread_t with > > rte_thread_set_name that operates on rte_thread_t. > > > > We should try to align tracing output from the EAL for all platforms > > but in this case we are retaining an exception for linux as requested > > from the community. > > > > v6: > > * clean up commit descriptions > > * add patch to set worker thread name on windows > > * remove __rte_deprecated from rte_thread_setname > > The unit tests are failing in the UNH Windows env though it was fine with v5. > https://lab.dpdk.org/results/dashboard/patchsets/25031/ > > 1/91 DPDK:fast-tests / acl_autotest FAIL > 1.05s (exit status 3221225477 or signal 3221225349 SIGinvalid) > 06:02:25 MALLOC_PERTURB_=92 DPDK_TEST=acl_autotest > C:\Users\builder\jenkins\workspace\Generic-VM-Unit-Test-DPDK\dpdk\build\app\test\dpdk-test.exe > ----------------------------------- output ----------------------------------- > stderr: > EAL: Detected CPU lcores: 4 > > EAL: Detected NUMA nodes: 1 > > EAL: Multi-process support is requested, but not available. > > ------------------------------------------------------------------------------ > > Could you have a look?
it's a bug in the windows implementation, v7 will be submitted to fix it. thankfully you asked for the eal worker thread initialization to be made consistent with freebsd/linux. it was that change that caused the failure to be exposed in this revision of the series. thank you.
