On Sun, May 02, 2021 at 05:33:33AM +0300, Dmitry Kozlyuk wrote:
> Interrupt manager in Windows EAL allocates on IOCP and starts
> a control thread that runs indefinitely. At DPDK cleanup
> this thread was not stopped and IOCP handle was not closed.
>
> Gracefully stop interrupt-handling in rte_eal_cleanup().
> The thread already closes IOCP handle before exiting.
>
> Fixes: 5c016fc0205a ("eal/windows: add interrupt thread skeleton")
> Cc: sta...@dpdk.org
>
> Signed-off-by: Dmitry Kozlyuk <dmitry.kozl...@gmail.com>
Acked-by: Jie Zhou <j...@microsoft.com>
Tested-by: Jie Zhou <j...@microsoft.com>
> ---
> lib/eal/windows/eal.c | 1 +
> lib/eal/windows/eal_interrupts.c | 26 ++++++++++++++++++++++++--
> lib/eal/windows/eal_windows.h | 5 +++++
> 3 files changed, 30 insertions(+), 2 deletions(-)
Enabled a subset of Unit test on Windows and when running alarm_autotest,
system hang at rte_eal_alarm_set. After applying this patch set, no repro any
more. Also system hang at pmd_perf_autotest and no repro with the patch. It is
with Intel i40e.
