From: Stephen Hemminger <stephen@networkplumber.org>
To: Antonio Di Bacco <antonio.di-bacco@keysight.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Accessing TLS for EAL threads
Date: Thu, 18 Nov 2021 08:26:37 -0800 [thread overview]
Message-ID: <20211118082637.24ca9876@hermes.local> (raw)
In-Reply-To: <DM6PR17MB3546109A8DE0870AF76DBE43BD999@DM6PR17MB3546.namprd17.prod.outlook.com>
On Tue, 16 Nov 2021 17:38:43 +0000
Antonio Di Bacco <antonio.di-bacco@keysight.com> wrote:
> I need to emulate the pthread_setspecific and pthread_getspecific for EAL threads. I don't find any suitable APIs in the DPDK to access the TLS and get and set keys.
>
> I launched a number of threads using the rte_eal_remote launch but I don't find any API that allows me to access the TLS for those threads.
There is not an API for a thread to access another threads local storage directly.
The DPDK TLS is wrapper around the glibc (and Windows) implementation of TLS.
For particular data structures, you can create a global data structure that is an
array of pointers indexed by lcore, and each lcore fills in itself.
Or do a more complex API via message passing.
prev parent reply other threads:[~2021-11-18 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 17:38 Antonio Di Bacco
2021-11-18 7:36 ` Pavel Vazharov
2021-11-18 16:26 ` Stephen Hemminger [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211118082637.24ca9876@hermes.local \
--to=stephen@networkplumber.org \
--cc=antonio.di-bacco@keysight.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).