From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailout2.w1.samsung.com (mailout2.w1.samsung.com [210.118.77.12]) by dpdk.org (Postfix) with ESMTP id 664A5C4D2 for ; Fri, 19 Feb 2016 07:33:00 +0100 (CET) Received: from eucpsbgm2.samsung.com (unknown [203.254.199.245]) by mailout2.w1.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTP id <0O2S00E3N7IZKO70@mailout2.w1.samsung.com> for dev@dpdk.org; Fri, 19 Feb 2016 06:32:59 +0000 (GMT) X-AuditID: cbfec7f5-f79b16d000005389-56-56c6b71a53eb Received: from eusync4.samsung.com ( [203.254.199.214]) by eucpsbgm2.samsung.com (EUCPMTA) with SMTP id FB.48.21385.A17B6C65; Fri, 19 Feb 2016 06:32:58 +0000 (GMT) Received: from imaximets.rnd.samsung.ru ([106.109.129.180]) by eusync4.samsung.com (Oracle Communications Messaging Server 7.0.5.31.0 64bit (built May 5 2014)) with ESMTPA id <0O2S00G447IL8D70@eusync4.samsung.com>; Fri, 19 Feb 2016 06:32:58 +0000 (GMT) From: Ilya Maximets To: dev@dpdk.org, Huawei Xie , Yuanhan Liu Date: Fri, 19 Feb 2016 09:32:43 +0300 Message-id: <1455863563-15751-5-git-send-email-i.maximets@samsung.com> X-Mailer: git-send-email 2.5.0 In-reply-to: <1455863563-15751-1-git-send-email-i.maximets@samsung.com> References: <1455863563-15751-1-git-send-email-i.maximets@samsung.com> X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGLMWRmVeSWpSXmKPExsVy+t/xa7pS24+FGVz4a23x7tN2Jov2mWeZ LK60/2S3mDjJxGL60wiLybOlLK5PuMDqwO6x4UQ/q8evBUtZPRbvecnkcefaHjaPeScDPfq2 rGIMYIvisklJzcksSy3St0vgyrjb1M9asJSjYtW72WwNjDPZuxg5OSQETCTezVrPCGGLSVy4 t56ti5GLQ0hgKaPEvfNzWSCcViaJX28OgVWxCehInFp9BMwWEUiQOLL/NytIEbPAMkaJiycm M4EkhAVCJRbPeAu2gkVAVeLIvmYWEJtXwE3idssboBoOoHVyEgsupIOEOQXcJb5sagGbKQRU 0nd2F+MERt4FjAyrGEVTS5MLipPSc430ihNzi0vz0vWS83M3MUJC6+sOxqXHrA4xCnAwKvHw VugdCxNiTSwrrsw9xCjBwawkwqvrDxTiTUmsrEotyo8vKs1JLT7EKM3BoiTOO3PX+xAhgfTE ktTs1NSC1CKYLBMHp1QDo9XtmHnN0joWpfNT6l4d+Nmx2/vaF9+o0l5TwS/Jij2PK0LP1GnZ 3n9iu6VfbMHZL0JGXbN/vnkhGF6gvX7TpZKL787MWi/kZnzF8FPj3q9Ppxf9EP+x7yzjB8sP e1vertnTFWC9/zm3m+GaWX8Z1nvcWW5es+Xaol2NbySZQ1afjnHQkTlp3avEUpyRaKjFXFSc CADgoJzXKQIAAA== Cc: Ilya Maximets , Dyasly Sergey Subject: [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 06:33:00 -0000 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. Performance Insensitive API --------------------------- -- 2.5.0