From: Tetsuya Mukawa <mukawa@igel.co.jp>
To: "Xie, Huawei" <huawei.xie@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "haifeng.lin@intel.com" <haifeng.lin@intel.com>,
"ann.zhuangyanying@huawei.com" <ann.zhuangyanying@huawei.com>
Subject: Re: [dpdk-dev] [RFC PATCH] vhost: remove lockless enqueue to virt ring
Date: Fri, 6 Nov 2015 10:42:48 +0900 [thread overview]
Message-ID: <563C0598.1040205@igel.co.jp> (raw)
In-Reply-To: <C37D651A908B024F974696C65296B57B4B16D482@SHSMSX101.ccr.corp.intel.com>
On 2015/11/05 19:21, Xie, Huawei wrote:
> If no objections, would remove the internal cmpset enqueue, should get
> some improved performance.
>
> No idea why commit message is lost:
> DPDK doesn't support receiving/transmitting packets from/to the same
> port/queue.
> Vhost pmd wraps vhost device as normal dpdk port. dpdkvhost based
> applications/switch
> also treate virtio port and physical port both as ports, and have
> their own
> lock implmentation when to enqueue packets to the same port. This patch
> removes
> the internal lockless vhost enqueue implmentation.
> On 11/5/2015 5:38 PM, Huawei Xie wrote:
>> Signed-off-by: Huawei Xie <huawei.xie@intel.com>
Hi Xie,
I think it's a good optimization.
But I guess the patch will changes behavior of vhost library API.
For example, if someone has already implemented an application based on
the assumption that vhost library has internal lock, I doubt their
application will face an issue with this patch.
If it's correct, we might need to follow below steps.
http://dpdk.org/doc/guides/contributing/versioning.html
Thanks,
Tetsuya
next prev parent reply other threads:[~2015-11-06 1:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1446658952-101192-1-git-send-email-huawei.xie@intel.com>
2015-11-05 10:21 ` Xie, Huawei
2015-11-06 1:42 ` Tetsuya Mukawa [this message]
2015-11-06 5:33 ` Xie, Huawei
2015-11-06 1:47 ` Changchun Ouyang
2015-11-06 5:50 ` Xie, Huawei
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=563C0598.1040205@igel.co.jp \
--to=mukawa@igel.co.jp \
--cc=ann.zhuangyanying@huawei.com \
--cc=dev@dpdk.org \
--cc=haifeng.lin@intel.com \
--cc=huawei.xie@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).