[dpdk-dev] [PATCH RFC 4/4] doc: add note about rte_vhost_enqueue_burst thread safety.

[Ilya Maximets]

Signed-off-by: Ilya Maximets <i.maximets at 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.
 
 Performance Insensitive API
 ---------------------------
-- 
2.5.0