[dpdk-dev] mempool: remove non-EAL thread note from header
Checks
Commit Message
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(-)
@@ -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>