d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

mempool: update non-EAL thread note

Browse Source 
Commit 30e6399892 ("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, and replaces it with a more up-to-date note.

Signed-off-by: Gage Eads <gage.eads@intel.com>
Acked-by: Olivier Matz <olivier.matz@6wind.com>
This commit is contained in:
Gage Eads 2017-03-30 18:02:00 -05:00 committed by Thomas Monjalon
parent ba82829fda
commit 8477f2f50d
1 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
lib/librte_mempool/rte_mempool.h
View File

@ -51,13 +51,15 @@
* meta-data in the object data and retrieve them when allocating a
* new object.
*
* 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.
* Note: the mempool implementation is not preemptible. An lcore must not be
* interrupted by another task that uses the same mempool (because it uses a
* ring which is not preemptible). Also, usual mempool functions like
* rte_mempool_get() or rte_mempool_put() are designed to be called from an EAL
* thread due to the internal per-lcore cache. Due to the lack of caching,
* rte_mempool_get() or rte_mempool_put() performance will suffer when called
* by non-EAL threads. Instead, non-EAL threads should call
* rte_mempool_generic_get() or rte_mempool_generic_put() with a user cache
* created with rte_mempool_cache_create().
*/
#include <stdio.h>