From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Parav Pandit <parav@nvidia.com>,
virtio-comment@lists.linux.dev, cohuck@redhat.com,
mvaralar@redhat.com, Jason Wang <jasowang@redhat.com>,
shahafs@nvidia.com, Willem de Bruijn <willemb@google.com>,
Daniel Verkamp <dverkamp@chromium.org>
Subject: Re: [PATCH v1] virtio-net: Fix to avoid using reserved feature bits
Date: Mon, 28 Apr 2025 04:47:08 -0400 [thread overview]
Message-ID: <20250428044458-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <bb5dd95a-15d5-4785-822c-e2b1e773950c@redhat.com>
On Mon, Apr 28, 2025 at 10:39:59AM +0200, Paolo Abeni wrote:
> On 4/23/25 8:07 PM, Michael S. Tsirkin wrote:
> > On Wed, Apr 23, 2025 at 09:29:11AM -0700, Daniel Verkamp wrote:
> >> On Tue, Apr 22, 2025 at 10:46 PM Michael S. Tsirkin <mst@redhat.com> wrote:
> >>> I'm afraid we'll have to bite the bullet.
> >>
> >> One other issue with bits > 63 is that the vhost-user protocol
> >> VHOST_USER_GET_FEATURES and VHOST_USER_SET_FEATURES messages use u64
> >> to represent the features, so vhost-user-net devices can't query or
> >> enable these features. vhost-user is outside the scope of the virtio
> >> spec, though, and I think it's reasonable to extend the protocol to
> >> enable high feature bits rather than avoiding them forever.
> >
> > Yes you would use VHOST_USER_SET_PROTOCOL_FEATURES to make VHOST_USER_GET_FEATURES
> > return two u64s, or even a new message returning an array.
>
> I think that additionally the VIRTIO_NET_CTRL_GUEST_OFFLOADS_SET command
> will need some clarification, as in the current text looks a bit
> inconsistent:
>
> """
> // in Offloads State Configuration / Setting Offloads State:
>
> #define VIRTIO_NET_F_GUEST_UDP_TUNNEL_GSO 46
>
> // ...
>
> The class VIRTIO_NET_CTRL_GUEST_OFFLOADS has one command:
> VIRTIO_NET_CTRL_GUEST_OFFLOADS_SET applies the new offloads configuration.
>
> le64 value passed as command data is a bitmask, bits set define
> offloads to be enabled, bits cleared - offloads to be disabled.
>
> There is a corresponding device feature for each offload. Upon feature
> negotiation corresponding offload gets enabled to preserve backward
> compatibility
> """
>
> The "corresponding device feature" has the same numerical value of the
> selected offloads, except for UDP tunnels related one (which are mapped
> to bits corresponding to reserved features).
>
> It's unclear to me which should be the better way to address this
> inconsistency.
>
> /P
Could you pls explain what is inconsistent?
--
MST
next prev parent reply other threads:[~2025-04-28 8:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-26 6:20 [PATCH v1] virtio-net: Fix to avoid using reserved feature bits Parav Pandit
2025-01-26 9:19 ` Michael S. Tsirkin
2025-01-26 16:44 ` Parav Pandit
2025-01-26 16:50 ` Michael S. Tsirkin
2025-01-27 9:21 ` Cornelia Huck
2025-01-27 12:54 ` Parav Pandit
2025-04-22 17:49 ` Paolo Abeni
2025-04-23 5:46 ` Michael S. Tsirkin
2025-04-23 16:05 ` Paolo Abeni
2025-04-28 9:13 ` Michael S. Tsirkin
2025-04-28 17:07 ` Paolo Abeni
2025-04-28 17:18 ` Michael S. Tsirkin
2025-04-23 16:29 ` Daniel Verkamp
2025-04-23 18:07 ` Michael S. Tsirkin
2025-04-28 8:39 ` Paolo Abeni
2025-04-28 8:47 ` Michael S. Tsirkin [this message]
2025-04-29 20:43 ` Michael S. Tsirkin
2025-04-30 4:44 ` Parav Pandit
2025-04-30 5:25 ` Yuri Benditovich
2025-04-30 5:44 ` Parav Pandit
2025-04-30 10:12 ` Paolo Abeni
2025-04-30 10:54 ` Parav Pandit
2025-05-01 13:42 ` Michael S. Tsirkin
2025-05-01 15:57 ` Paolo Abeni
2025-05-06 6:15 ` Parav Pandit
2025-05-06 7:56 ` Michael S. Tsirkin
2025-05-06 8:56 ` Parav Pandit
2025-05-06 14:38 ` Paolo Abeni
2025-05-06 15:00 ` Parav Pandit
2025-05-06 15:40 ` Paolo Abeni
2025-05-06 16:20 ` Parav Pandit
2025-05-07 9:57 ` Paolo Abeni
2025-05-08 6:15 ` Michael S. Tsirkin
2025-05-19 8:57 ` Paolo Abeni
2025-05-19 9:04 ` Parav Pandit
2025-05-19 9:24 ` Paolo Abeni
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=20250428044458-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=dverkamp@chromium.org \
--cc=jasowang@redhat.com \
--cc=mvaralar@redhat.com \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.linux.dev \
--cc=willemb@google.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