From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Ilya Maximets <i.maximets@samsung.com>
Cc: Flavio Leitner <fbl@sysclose.org>, "dev@dpdk.org" <dev@dpdk.org>,
Sergey Dyasly <s.dyasly@samsung.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
"Xie, Huawei" <huawei.xie@intel.com>
Subject: Re: [dpdk-dev] [RFC] vhost-user public struct refactor (was Re: [PATCH RFC 2/4] vhost: make buf vector for scatter RX) local.
Date: Wed, 6 Apr 2016 13:38:00 +0800 [thread overview]
Message-ID: <20160406053800.GU3080@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <506067238.174981459919460416.JavaMail.weblogic@eumlwas01>
On Wed, Apr 06, 2016 at 05:11:01AM +0000, Ilya Maximets wrote:
> > There is a plan to use vHost PMD, so from OVS point of view the virtio
> > stuff would be hidden because vhost PMD would look like just as a
> > regular ethernet, right?
>
> But we still need to have access to virtqueue_enabe/disable notifications to
> work properly. How this will be done if virtqueue will be hidden from user?
Do you mean vring_state_changed() callback? It will not be removed.
BTW, when using vhost pmd, you will not be aware of such callback:
it will be translated to a RTE_ETH_EVENT_QUEUE_STATE interrupt.
OTOH, I have a simple git grep of "vq" from ovs dpdk netdev code,
it returns nothing. So, I don't think that will matter?
--yliu
next prev parent reply other threads:[~2016-04-06 5:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 5:11 Ilya Maximets
2016-04-06 5:38 ` Yuanhan Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-06 6:00 Ilya Maximets
2016-02-19 6:32 [dpdk-dev] [PATCH RFC 0/4] Thread safe rte_vhost_enqueue_burst() Ilya Maximets
2016-02-19 6:32 ` [dpdk-dev] [PATCH RFC 2/4] vhost: make buf vector for scatter RX local Ilya Maximets
2016-02-19 7:06 ` Yuanhan Liu
2016-04-05 5:47 ` [dpdk-dev] [RFC] vhost-user public struct refactor (was Re: [PATCH RFC 2/4] vhost: make buf vector for scatter RX) local Yuanhan Liu
2016-04-05 8:37 ` Thomas Monjalon
2016-04-05 14:06 ` Yuanhan Liu
2016-04-06 4:14 ` Flavio Leitner
2016-04-06 4:54 ` Yuanhan Liu
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=20160406053800.GU3080@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=dev@dpdk.org \
--cc=fbl@sysclose.org \
--cc=huawei.xie@intel.com \
--cc=i.maximets@samsung.com \
--cc=s.dyasly@samsung.com \
--cc=thomas.monjalon@6wind.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).