From: Tal Shnaiderman <talshn@nvidia.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, pallavi.kadam@intel.com,
dmitry.kozliuk@gmail.com, navasile@linux.microsoft.com,
dmitrym@microsoft.com
Subject: [dpdk-dev] [PATCH] eal/windows: add pthread TLS function support
Date: Sun, 13 Dec 2020 22:00:15 +0200 [thread overview]
Message-ID: <20201213200015.5932-1-talshn@nvidia.com> (raw)
Add the following functions to the pthread shim implementation
for Windows as they are needed for thread safe rte_flow functions.
pthread_key_create.
pthread_key_delete.
pthread_getspecific.
pthread_setspecific.
Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
---
lib/librte_eal/windows/include/pthread.h | 42 ++++++++++++++++++++++++++++++++
1 file changed, 42 insertions(+)
diff --git a/lib/librte_eal/windows/include/pthread.h b/lib/librte_eal/windows/include/pthread.h
index fb11a07ce6..e0c08fe5d6 100644
--- a/lib/librte_eal/windows/include/pthread.h
+++ b/lib/librte_eal/windows/include/pthread.h
@@ -34,6 +34,8 @@ typedef CRITICAL_SECTION pthread_mutex_t;
typedef SYNCHRONIZATION_BARRIER pthread_barrier_t;
+typedef DWORD pthread_key_t;
+
#define pthread_barrier_init(barrier, attr, count) \
InitializeSynchronizationBarrier(barrier, count, -1)
#define pthread_barrier_wait(barrier) EnterSynchronizationBarrier(barrier, \
@@ -179,6 +181,46 @@ pthread_mutex_destroy(pthread_mutex_t *mutex)
return 0;
}
+static inline int
+pthread_key_create(pthread_key_t *key,
+ __rte_unused void (*destructor)(void*))
+{
+ if (((*key) = TlsAlloc()) == TLS_OUT_OF_INDEXES) {
+ RTE_LOG_WIN32_ERR("TlsAlloc()");
+ return ENOMEM;
+ }
+ return 0;
+}
+
+static inline int
+pthread_key_delete(pthread_key_t key)
+{
+ if (!TlsFree(key)) {
+ RTE_LOG_WIN32_ERR("TlsFree()");
+ return -1;
+ }
+ return 0;
+}
+
+static inline void *
+pthread_getspecific(pthread_key_t key)
+{
+ return TlsGetValue(key);
+}
+
+static inline int
+pthread_setspecific(pthread_key_t key, const void *value)
+{
+ /* discard const qualifier */
+ char *p = (char *) (uintptr_t) value;
+
+ if (!TlsSetValue(key, p)) {
+ RTE_LOG_WIN32_ERR("TlsSetValue()");
+ return -1;
+ }
+ return 0;
+}
+
#ifdef __cplusplus
}
#endif
--
2.16.1.windows.4
reply other threads:[~2020-12-13 20:02 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=20201213200015.5932-1-talshn@nvidia.com \
--to=talshn@nvidia.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=thomas@monjalon.net \
/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).