DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] Retrieving lcore worker thread id
@ 2020-07-14 12:03 Mattias Rönnblom
  2020-07-14 13:08 ` Van Haaren, Harry
  0 siblings, 1 reply; 11+ messages in thread
From: Mattias Rönnblom @ 2020-07-14 12:03 UTC (permalink / raw)
  To: dpdk-dev; +Cc: Tomasz Piatkowski

Hi.

In DPDK 19.11, the lcore_config struct of <rte_lcore.h> is made private, 
and with it the possibility to look up the thread id of the lcore worker 
threads disappears.

One use case is an application with a monitoring function (on some 
control plane thread), which uses the thread ids to make sure the worker 
threads gets the CPU runtime they should, and thus is able to detect 
stalls.

Is there some other way of finding out the thread_id of a lcore worker 
thread? All I can think of are hacks like using a temporary service 
function for service cores, in combination with requiring launched 
application threads also to store their thread id in some global 
structure (index by lcore_id).

Is there some cleaner way? If not, would adding something like a 
rte_lcore_thread_id() function make sense?

Regards,
     Mattias


^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2020-10-20 18:40 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-14 12:03 [dpdk-dev] Retrieving lcore worker thread id Mattias Rönnblom
2020-07-14 13:08 ` Van Haaren, Harry
2020-07-14 18:59   ` Honnappa Nagarahalli
2020-07-14 20:51     ` Stephen Hemminger
2020-07-15 10:17       ` Mattias Rönnblom
2020-07-15 16:21         ` Stephen Hemminger
2020-07-16 10:20           ` Mattias Rönnblom
2020-08-10  9:36             ` [dpdk-dev] [RFC] eal: introduce function to get lcore " Mattias Rönnblom
2020-10-20 13:38               ` David Marchand
2020-10-20 18:40                 ` Mattias Rönnblom
2020-07-15 10:21   ` [dpdk-dev] Retrieving lcore worker " Mattias Rönnblom

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).