From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1330] rte_thread_* wrappers missing in DPDK
Date: Thu, 23 Nov 2023 14:32:43 +0000 [thread overview]
Message-ID: <bug-1330-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1330
Bug ID: 1330
Summary: rte_thread_* wrappers missing in DPDK
Product: DPDK
Version: 23.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: vodak@cesnet.cz
Target Milestone: ---
In DPDK 23.11, rte_ctrl_thread_create has been replaced by
rte_thread_create_control, encouraging Linux users to switch from the pthread_t
API to the rte_thread API.
The problem is that the rte_thread API does not currently provide wrappers for
all pthread functions. There are no equivalent functions for
pthread_timedjoin_np, pthread_getname_np and pthread_cancel.
Would it be possible to add support for these functions as well?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2836 bytes --]
reply other threads:[~2023-11-23 14:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1330-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).