From: David Marchand <david.marchand@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, chenbo.xia@intel.com
Subject: Re: [PATCH 1/2] vhost: fix vduse features negotiation
Date: Wed, 5 Jul 2023 15:36:23 +0200 [thread overview]
Message-ID: <CAJFAV8yyrDPpaG_f1=FOWHmpoZcLFB_L8kRAmd4yvVLGg+REeg@mail.gmail.com> (raw)
In-Reply-To: <20230705132232.114266-2-maxime.coquelin@redhat.com>
On Wed, Jul 5, 2023 at 3:22 PM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
> @@ -950,9 +954,14 @@ rte_vhost_driver_register(const char *path, uint64_t flags)
> * two values.
> */
> vsocket->use_builtin_virtio_net = true;
> - vsocket->supported_features = VIRTIO_NET_SUPPORTED_FEATURES;
> - vsocket->features = VIRTIO_NET_SUPPORTED_FEATURES;
> - vsocket->protocol_features = VHOST_USER_PROTOCOL_FEATURES;
> + if (vsocket->is_vduse) {
> + vsocket->supported_features = VDUSE_NET_SUPPORTED_FEATURES;
> + vsocket->features = VDUSE_NET_SUPPORTED_FEATURES;
> + } else {
> + vsocket->supported_features = VIRTIO_NET_SUPPORTED_FEATURES;
> + vsocket->features = VIRTIO_NET_SUPPORTED_FEATURES;
> + vsocket->protocol_features = VHOST_USER_PROTOCOL_FEATURES;
> + }
>
Would it make sense to split those features in a set of features
shared by vhost-user and vduse, and one dedicated set for each of
them?
For example, the VIRTIO_NET_F_GUEST/HOST_* features are not bound to
vhost-user / vduse, are they?
--
David Marchand
next prev parent reply other threads:[~2023-07-05 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 13:22 [PATCH 0/2] VDUSE fixes for v23.07 Maxime Coquelin
2023-07-05 13:22 ` [PATCH 1/2] vhost: fix vduse features negotiation Maxime Coquelin
2023-07-05 13:36 ` David Marchand [this message]
2023-07-05 17:02 ` Maxime Coquelin
2023-07-05 17:15 ` David Marchand
2023-07-05 13:22 ` [PATCH 2/2] vduse: fix missing event index features Maxime Coquelin
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='CAJFAV8yyrDPpaG_f1=FOWHmpoZcLFB_L8kRAmd4yvVLGg+REeg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=chenbo.xia@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.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).