From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gage Eads Subject: [PATCH] mempool: remove non-EAL thread note from header Date: Mon, 20 Mar 2017 21:34:40 -0500 Message-ID: <1490063680-13969-1-git-send-email-gage.eads@intel.com> Cc: olivier.matz@6wind.com To: dev@dpdk.org Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 1347D3B5 for ; Tue, 21 Mar 2017 03:34:49 +0100 (CET) List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 --- 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 -- 2.7.4