[PATCH v3] mempool: remove non-EAL thread note from header
From: Gage Eads <hidden>
Date: 2017-03-23 14:21:06
Subsystem:
library code, the rest · Maintainers:
Andrew Morton, Linus Torvalds
From: Gage Eads <hidden>
Date: 2017-03-23 14:21:06
Subsystem:
library code, the rest · Maintainers:
Andrew Morton, Linus Torvalds
Commit 30e6399892276 ("mempool: support non-EAL thread") added the
capability for non-EAL threads to use the mempool library. 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 <redacted>
---
v2: Changed commit message to referenced commit 30e63998 instead of 4b5062755
v3: Fix checkpatch error
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