From: Tiwei Bie <tiwei.bie@intel.com>
To: junjie.j.chen@intel.com
Cc: yliu@fridaylinux.org, maxime.coquelin@redhat.com,
jianfeng.tan@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] vhost: support virtqueue interrupt/notification suppression
Date: Tue, 28 Nov 2017 10:46:35 +0800 [thread overview]
Message-ID: <20171128024635.5zouuhptqbbv3bsx@deepin-15.5-oivbkq> (raw)
In-Reply-To: <20171128094826.179454-1-junjie.j.chen@intel.com>
Hi,
On Tue, Nov 28, 2017 at 04:48:26AM -0500, junjie.j.chen@intel.com wrote:
[...]
> @@ -195,6 +197,10 @@ struct vhost_msg {
>
> #define VHOST_USER_F_PROTOCOL_FEATURES 30
>
> +#ifndef VIRTIO_F_EVENT_IDX
> + #define VIRTIO_F_EVENT_IDX 29
> +#endif
> +
> /* Features supported by this builtin vhost-user net driver. */
> #define VIRTIO_NET_SUPPORTED_FEATURES ((1ULL << VIRTIO_NET_F_MRG_RXBUF) | \
> (1ULL << VIRTIO_NET_F_CTRL_VQ) | \
> @@ -212,7 +218,8 @@ struct vhost_msg {
> (1ULL << VIRTIO_NET_F_GUEST_TSO6) | \
> (1ULL << VIRTIO_RING_F_INDIRECT_DESC) | \
> (1ULL << VIRTIO_NET_F_MTU) | \
> - (1ULL << VIRTIO_F_IOMMU_PLATFORM))
> + (1ULL << VIRTIO_F_IOMMU_PLATFORM) | \
> + (1ULL << VIRTIO_F_EVENT_IDX))
>
You can use VIRTIO_RING_F_EVENT_IDX directly. It has already
been defined by Linux. And you can add this new feature bit
after VIRTIO_RING_F_INDIRECT_DESC:
diff --git i/lib/librte_vhost/vhost.h w/lib/librte_vhost/vhost.h
index 2f36a034e..350ac3acc 100644
--- i/lib/librte_vhost/vhost.h
+++ w/lib/librte_vhost/vhost.h
@@ -211,6 +211,7 @@ struct vhost_msg {
(1ULL << VIRTIO_NET_F_GUEST_TSO4) | \
(1ULL << VIRTIO_NET_F_GUEST_TSO6) | \
(1ULL << VIRTIO_RING_F_INDIRECT_DESC) | \
+ (1ULL << VIRTIO_RING_F_EVENT_IDX) | \
(1ULL << VIRTIO_NET_F_MTU) | \
(1ULL << VIRTIO_F_IOMMU_PLATFORM))
Best regards,
Tiwei
prev parent reply other threads:[~2017-11-28 2:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 9:48 junjie.j.chen
2017-11-28 2:46 ` Tiwei Bie [this message]
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=20171128024635.5zouuhptqbbv3bsx@deepin-15.5-oivbkq \
--to=tiwei.bie@intel.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=junjie.j.chen@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=yliu@fridaylinux.org \
/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).