From mboxrd@z Thu Jan  1 00:00:00 1970
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Subject: Re: [PATCH RFC 4/4] doc: add note about
 rte_vhost_enqueue_burst thread safety.
Date: Fri, 19 Feb 2016 15:10:46 +0800
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
Cc: dev@dpdk.org, Dyasly Sergey <s.dyasly@samsung.com>
To: Ilya Maximets <i.maximets@samsung.com>,
 "Xie, Huawei" <huawei.xie@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93])
 by dpdk.org (Postfix) with ESMTP id D8A56C39E
 for <dev@dpdk.org>; Fri, 19 Feb 2016 08:10:10 +0100 (CET)
Content-Disposition: inline
In-Reply-To: <1455863563-15751-5-git-send-email-i.maximets@samsung.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Fri, Feb 19, 2016 at 09:32:43AM +0300, Ilya Maximets wrote:
> Signed-off-by: Ilya Maximets <i.maximets@samsung.com>
> ---
>  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