DPDK patches and discussions
 help / color / mirror / Atom feed
From: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Tomasz Piatkowski <tomasz.piatkowski@ericsson.com>
Subject: [dpdk-dev] Retrieving lcore worker thread id
Date: Tue, 14 Jul 2020 12:03:54 +0000
Message-ID: <ef4624e4-46ca-767a-ee02-af43c96bcba1@ericsson.com> (raw)


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 

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?


             reply	other threads:[~2020-07-14 12:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 12:03 Mattias Rönnblom [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ef4624e4-46ca-767a-ee02-af43c96bcba1@ericsson.com \
    --to=mattias.ronnblom@ericsson.com \
    --cc=dev@dpdk.org \
    --cc=tomasz.piatkowski@ericsson.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git