From: Gage Eads <gage.eads@intel.com>
To: dev@dpdk.org
Cc: olivier.matz@6wind.com
Subject: [dpdk-dev] [PATCH] mempool: remove non-EAL thread note from header
Date: Mon, 20 Mar 2017 21:34:40 -0500 [thread overview]
Message-ID: <1490063680-13969-1-git-send-email-gage.eads@intel.com> (raw)
Commit 4b5062755aa7 ("mempool: allow user-owned cache") added the
capability for non-EAL threads to use the mempool library by checking
rte_lcore_id() before accessing the per-lcore cache. This commit
removes the note indicating that the mempool library cannot be used
safely by non-EAL threads.
Also, fix a typo.
Signed-off-by: Gage Eads <gage.eads@intel.com>
---
lib/librte_mempool/rte_mempool.h | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/lib/librte_mempool/rte_mempool.h b/lib/librte_mempool/rte_mempool.h
index 991feaa..b1186fd 100644
--- a/lib/librte_mempool/rte_mempool.h
+++ b/lib/librte_mempool/rte_mempool.h
@@ -53,11 +53,7 @@
*
* Note: the mempool implementation is not preemptable. A lcore must
* not be interrupted by another task that uses the same mempool
- * (because it uses a ring which is not preemptable). Also, mempool
- * functions must not be used outside the DPDK environment: for
- * example, in linuxapp environment, a thread that is not created by
- * the EAL must not use mempools. This is due to the per-lcore cache
- * that won't work as rte_lcore_id() will not return a correct value.
+ * (because it uses a ring which is not preemptible).
*/
#include <stdio.h>
--
2.7.4
next reply other threads:[~2017-03-21 2:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 2:34 Gage Eads [this message]
2017-03-22 17:04 ` [dpdk-dev] [PATCH v2] " Gage Eads
2017-03-23 14:20 ` [dpdk-dev] [PATCH v3] " Gage Eads
2017-03-24 14:04 ` Olivier Matz
2017-03-29 15:30 ` Eads, Gage
2017-03-30 15:12 ` Olivier Matz
2017-03-30 23:02 ` [dpdk-dev] [PATCH v4] mempool: update non-EAL thread note in the header Gage Eads
2017-03-31 13:51 ` Olivier Matz
2017-04-03 16:32 ` Thomas Monjalon
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=1490063680-13969-1-git-send-email-gage.eads@intel.com \
--to=gage.eads@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
/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).