[dpdk-dev] [PATCH 0/7] support set thread name

[Power, Ciara]

>-----Original Message-----
>From: David Marchand <david.marchand at redhat.com>
>Sent: Monday 12 April 2021 08:20
>To: Min Hu (Connor) <humin29 at huawei.com>; Shepard Siegel
><shepard.siegel at atomicrules.com>; Yang, Qiming <qiming.yang at intel.com>;
>Wang, Xiao W <xiao.w.wang at intel.com>; Xu, Rosen <rosen.xu at intel.com>;
>Maxime Coquelin <maxime.coquelin at redhat.com>
>Cc: dev <dev at dpdk.org>; Yigit, Ferruh <ferruh.yigit at intel.com>; Mcnamara,
>John <john.mcnamara at intel.com>; Power, Ciara <ciara.power at intel.com>
>Subject: Re: [dpdk-dev] [PATCH 0/7] support set thread name
>
>On Sat, Apr 10, 2021 at 12:40 PM Min Hu (Connor) <humin29 at huawei.com>
>wrote:
>>
>> This set of patches support set thread name for debugging.
>>
>> Chengwen Feng (7):
>>   net/ark: support set thread name
>>   net/ice: support set VSI reset thread name
>>   vdpa/ifc: support set notify and vring relay thread name
>>   raw/ifpga: support set monitor thread name
>>   examples/performance-thread: support set thread name
>>   telemetry: support set init threads name
>>   examples/vhost_blk: support set ctrl worker thread name
>
>Rather than add those calls, can maintainers check if their component can use
>ctrl threads instead?
>rte_ctrl_thread_create ensures both that the name is set, and that the ctrl
>thread won't run on the same cpu as "datapath" threads.
>
>I also saw some issues with components creating threads.
>I'll post a series addressing those later (net/ark, net/ice not detaching/joining
>created threads + telemetry not checking pthread_create failures).
>
>

Hi David,

Telemetry has no dependency on EAL, so using the ctrl thread functions isn't possible for that component.

Thanks,
Ciara

>--
>David Marchand