From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id D8A56C39E for ; Fri, 19 Feb 2016 08:10:10 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP; 18 Feb 2016 23:10:09 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,469,1449561600"; d="scan'208";a="655475426" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.66.49]) by FMSMGA003.fm.intel.com with ESMTP; 18 Feb 2016 23:10:09 -0800 Date: Fri, 19 Feb 2016 15:10:46 +0800 From: Yuanhan Liu To: Ilya Maximets , "Xie, Huawei" Message-ID: <20160219071046.GT21426@yliu-dev.sh.intel.com> References: <1455863563-15751-1-git-send-email-i.maximets@samsung.com> <1455863563-15751-5-git-send-email-i.maximets@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1455863563-15751-5-git-send-email-i.maximets@samsung.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org, Dyasly Sergey Subject: Re: [dpdk-dev] [PATCH RFC 4/4] doc: add note about rte_vhost_enqueue_burst thread safety. X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2016 07:10:11 -0000 On Fri, Feb 19, 2016 at 09:32:43AM +0300, Ilya Maximets wrote: > Signed-off-by: Ilya Maximets > --- > doc/guides/prog_guide/thread_safety_dpdk_functions.rst | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/doc/guides/prog_guide/thread_safety_dpdk_functions.rst b/doc/guides/prog_guide/thread_safety_dpdk_functions.rst > index 403e5fc..13a6c89 100644 > --- a/doc/guides/prog_guide/thread_safety_dpdk_functions.rst > +++ b/doc/guides/prog_guide/thread_safety_dpdk_functions.rst > @@ -67,6 +67,7 @@ then locking, or some other form of mutual exclusion, is necessary. > The ring library is based on a lockless ring-buffer algorithm that maintains its original design for thread safety. > Moreover, it provides high performance for either multi- or single-consumer/producer enqueue/dequeue operations. > The mempool library is based on the DPDK lockless ring library and therefore is also multi-thread safe. > +rte_vhost_enqueue_burst() is also thread safe because based on lockless ring-buffer algorithm like the ring library. FYI, Huawei meant to make rte_vhost_enqueue_burst() not be thread-safe, to aligh with the usage of rte_eth_tx_burst(). --yliu