public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Heng Qi <hengqi@linux.alibaba.com>,
	"virtio-comment@lists.oasis-open.org"
	<virtio-comment@lists.oasis-open.org>,
	"virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	Jason Wang <jasowang@redhat.com>,
	Yuri Benditovich <yuri.benditovich@daynix.com>,
	Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
	Cornelia Huck <cohuck@redhat.com>
Subject: [virtio-dev] Re: [virtio-comment] Re: [PATCH v18] virtio-net: support inner header hash
Date: Wed, 21 Jun 2023 16:16:39 -0400	[thread overview]
Message-ID: <20230621161157-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481141E18AAF1BF214A0E29DC5DA@PH0PR12MB5481.namprd12.prod.outlook.com>

On Wed, Jun 21, 2023 at 07:37:00PM +0000, Parav Pandit wrote:
> 
> 
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Wednesday, June 21, 2023 3:32 PM
> 
> > 
> > Well RSS is designed (imho) better since it keeps the supported types in config
> > space. Doing it here would have removed the need for GET command.
> > Yes I know Parav hates config space, no I don't think for a read-only field like
> > this one this hate is justified.
> > Did we discuss this and decided not to add it in config space for some reason? I
> > don't remember ...
> > 
> Yes, we discussed this in v12 or before to have symmetric interface to have it via get and set via cvq.
> Should be there in the change log.

Oh good point, it is in commit log. Heng Qi, thanks for writing such a
nice detailed commit log!

Here is what you wrote:
	Given that a set command is added via cvq, it make sense to also do 
	symetrric work to get it via a cvq.

and actually I missed the fact that instead of making this
symmetric it forced separate structures for GET and SET.

If we move supported_tunnel_hash_types back to config space
then GET and SET just need the active bitmap. *that* seems
symmetric to me.

And the field is RO so no memory cost to exposing it in all VFs.


-- 
MST


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2023-06-21 20:17 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 13:50 [virtio-dev] [PATCH v18] virtio-net: support inner header hash Heng Qi
2023-06-21 15:38 ` [virtio-dev] " Michael S. Tsirkin
2023-06-21 16:46   ` [virtio-dev] Re: [virtio-comment] " Heng Qi
2023-06-21 17:52     ` [virtio-dev] " Parav Pandit
2023-06-21 19:25       ` [virtio-dev] " Michael S. Tsirkin
2023-06-21 19:28         ` [virtio-dev] " Parav Pandit
2023-06-21 19:35           ` [virtio-dev] " Michael S. Tsirkin
2023-06-21 19:39             ` [virtio-dev] " Parav Pandit
2023-06-21 19:45               ` [virtio-dev] " Michael S. Tsirkin
2023-06-22  0:46             ` Heng Qi
2023-06-21 19:32     ` Michael S. Tsirkin
2023-06-21 19:37       ` [virtio-dev] " Parav Pandit
2023-06-21 20:16         ` Michael S. Tsirkin [this message]
2023-06-21 20:24           ` Parav Pandit
2023-06-21 20:37             ` [virtio-dev] " Michael S. Tsirkin
2023-06-21 20:52               ` [virtio-dev] " Parav Pandit
2023-06-22  0:59                 ` Heng Qi
2023-06-22  1:04                   ` Parav Pandit
2023-06-22  1:17                     ` Heng Qi
2023-06-22  6:23                 ` [virtio-dev] " Michael S. Tsirkin
2023-06-22 12:32                   ` [virtio-dev] " Parav Pandit
2023-06-22 13:42                     ` [virtio-dev] " Heng Qi
2023-06-22 14:27                       ` [virtio-dev] " Parav Pandit
2023-06-22 16:46                         ` [virtio-dev] " Michael S. Tsirkin
2023-06-22 16:54                           ` [virtio-dev] " Parav Pandit
2023-06-22 17:03                             ` [virtio-dev] " Michael S. Tsirkin
2023-06-22 17:11                               ` [virtio-dev] " Parav Pandit
2023-06-22 17:28                                 ` [virtio-dev] " Michael S. Tsirkin
2023-06-22 17:58                                   ` [virtio-dev] " Parav Pandit
2023-06-28 10:41                                     ` [virtio-dev] " Michael S. Tsirkin
2023-06-28 16:46                                       ` [virtio-dev] " Parav Pandit
2023-06-28 17:08                                         ` [virtio-dev] " Michael S. Tsirkin
2023-06-22 16:28                     ` Michael S. Tsirkin
2023-06-22 16:42                       ` [virtio-dev] " Parav Pandit
2023-06-22 16:54                         ` [virtio-dev] " Michael S. Tsirkin
2023-06-22 17:04                           ` Parav Pandit
2023-06-22 17:14                             ` Michael S. Tsirkin
2023-06-22 17:20                               ` Parav Pandit
2023-06-22 17:43                                 ` Michael S. Tsirkin
2023-06-22 18:12                                   ` Parav Pandit
2023-06-22 18:36                                     ` Michael S. Tsirkin
2023-06-22 17:11                     ` Michael S. Tsirkin
2023-06-22 17:15                       ` [virtio-dev] " Parav Pandit
2023-06-22 17:37                         ` [virtio-dev] " Michael S. Tsirkin
2023-06-22 17:51                           ` Parav Pandit
2023-06-22 18:11                             ` Michael S. Tsirkin
2023-06-22 18:17                               ` Parav Pandit
2023-06-22 18:40                                 ` Michael S. Tsirkin
2023-06-22 18:50                                   ` [virtio-dev] RE: [virtio-comment] " Parav Pandit
2023-06-22 19:02                                     ` [virtio-dev] " Michael S. Tsirkin
2023-06-22 20:27                                       ` [virtio-dev] " Parav Pandit
2023-06-28 10:47                                         ` [virtio-dev] " Michael S. Tsirkin
2023-06-22  0:41       ` Heng Qi

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=20230621161157-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=hengqi@linux.alibaba.com \
    --cc=jasowang@redhat.com \
    --cc=parav@nvidia.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=xuanzhuo@linux.alibaba.com \
    --cc=yuri.benditovich@daynix.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