[dpdk-stable] [dpdk-dev] 19.11.9 patches review and test - V2

[Luc Pelletier]

> > # Basic Intel(R) NIC testing
> > * PF(i40e, ixgbe): test scenarios including rte_flow/TSO/Jumboframe/checksum offload/Tunnel, etc. Listed but not all.
> >         - Known issues as below:
> >         1) https://bugs.dpdk.org/show_bug.cgi?id=731 – [dpdk-19.11.9] telemetry: python3 /root/dpdk/usertools/dpdk-telemetry-client.py prompt connection refused)
> >                 Fixed commit  is af68c1d699be6c369e296b775bdbf13ae18b79cc eal: fix hang in control thread creation
>
> This one was in the candidate list of patches for 19.11.x, but it
> didn't apply cleanly.
> I've asked for a backport in my mail on 20th May - in this thread [1]
> But in the meantime that was all done and -rc2 that you have tested contains
>
> 34cc55cce6b1 ("eal: fix race in control thread creation")
> af68c1d699be ("eal: fix hang in control thread creation")
>
> In the form of these backports:
> $ git tag --contains 555da24882e1ca836f9532304f5f58034e57ff5e
> v19.11.9-rc2
> $ git tag --contains 0b8f4f0462f2260fc618e297e91317a891c6d255
> v19.11.9-rc2
>
> So if af68c1d699be really was meant to fix this known issue then it
> does not do so in 19.11.x.
> @Luc - I'm setting you to CC in case you happen to know why.

The patches I submitted are unrelated to telemetry. They're related to
control thread creation logic in the EAL. I don't know anything about
the telemetry code but I'd be surprised if my commits have anything to
do with the telemetry bug linked above.

Thanks.