DPDK usage discussions
 help / color / mirror / Atom feed
From: Antonio Di Bacco <antonio.di-bacco@keysight.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Accessing TLS for EAL threads
Date: Tue, 16 Nov 2021 17:38:43 +0000	[thread overview]
Message-ID: <DM6PR17MB3546109A8DE0870AF76DBE43BD999@DM6PR17MB3546.namprd17.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 318 bytes --]

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.





[-- Attachment #2: Type: text/html, Size: 2019 bytes --]

             reply	other threads:[~2021-11-18  7:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 17:38 Antonio Di Bacco [this message]
2021-11-18  7:36 ` Pavel Vazharov
2021-11-18 16:26 ` Stephen Hemminger

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=DM6PR17MB3546109A8DE0870AF76DBE43BD999@DM6PR17MB3546.namprd17.prod.outlook.com \
    --to=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).