From: Ilya Maximets <i.maximets@samsung.com>
To: dev@dpdk.org, Huawei Xie <huawei.xie@intel.com>,
Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: Ilya Maximets <i.maximets@samsung.com>,
Dyasly Sergey <s.dyasly@samsung.com>
Subject: [dpdk-dev] [PATCH RFC v2 0/3] Thread safe rte_vhost_enqueue_burst().
Date: Fri, 19 Feb 2016 13:56:37 +0300 [thread overview]
Message-ID: <1455879400-17827-1-git-send-email-i.maximets@samsung.com> (raw)
Implementation of rte_vhost_enqueue_burst() based on lockless ring-buffer
algorithm and contains almost all to be thread-safe, but it's not.
This set adds required changes.
First patch in set is a standalone patch that fixes many times discussed
issue with barriers on different architectures.
Second and third adds fixes to make rte_vhost_enqueue_burst thread safe.
version 2:
* Documentation patch dropped. Other patches of series still
may be merged to fix existing issues and keep code in
consistent state for the future.
* buf_vec field of struct vhost_virtqueue marked as deprecated.
Ilya Maximets (3):
vhost: use SMP barriers instead of compiler ones.
vhost: make buf vector for scatter RX local.
vhost: avoid reordering of used->idx and last_used_idx updating.
doc/guides/rel_notes/deprecation.rst | 1 +
lib/librte_vhost/rte_virtio_net.h | 2 +-
lib/librte_vhost/vhost_rxtx.c | 67 ++++++++++++++++++++----------------
3 files changed, 40 insertions(+), 30 deletions(-)
--
2.5.0
next reply other threads:[~2016-02-19 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 10:56 Ilya Maximets [this message]
2016-02-19 10:56 ` [dpdk-dev] [PATCH RFC v2 1/3] vhost: use SMP barriers instead of compiler ones Ilya Maximets
2016-02-19 10:56 ` [dpdk-dev] [PATCH RFC v2 2/3] vhost: make buf vector for scatter RX local Ilya Maximets
2016-02-19 10:56 ` [dpdk-dev] [PATCH RFC v2 3/3] vhost: avoid reordering of used->idx and last_used_idx updating Ilya Maximets
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1455879400-17827-1-git-send-email-i.maximets@samsung.com \
--to=i.maximets@samsung.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@intel.com \
--cc=s.dyasly@samsung.com \
--cc=yuanhan.liu@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).