From: Parav Pandit <parav@nvidia.com>
To: Cornelia Huck <cohuck@redhat.com>,
Heng Qi <hengqi@linux.alibaba.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Alvaro Karsz <alvaro.karsz@solid-run.com>,
David Edmondson <david.edmondson@oracle.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: RE: [virtio-comment] RE: [PATCH v13] virtio-net: support the virtqueue coalescing moderation
Date: Wed, 22 Mar 2023 16:46:36 +0000 [thread overview]
Message-ID: <PH0PR12MB5481F9FF6580D1F8847B9D3BDC869@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <87jzz8hh1w.fsf@redhat.com>
> From: Cornelia Huck <cohuck@redhat.com>
> Sent: Wednesday, March 22, 2023 12:44 PM
>
> >> Well, I think we want to avoid having to add a normative statement
> >> for the device, so we need to be strict with what the driver is allowed to do.
> > Drivers are untrusted entities.
> > device normative statement is needed, it will do the checks anyway where it
> is applying the config.
>
> But isn't that implementation specific? I.e. if the driver sends junk, the device
> needs to be able to deal with it in any case.
Not sure which part is implementation specific.
The device will deal with it and return an error code when supplied qid is invalid (of cvq or of disabled vq).
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2023-03-22 16:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 12:51 [virtio-comment] [PATCH v13] virtio-net: support the virtqueue coalescing moderation Heng Qi
2023-03-22 15:20 ` [virtio-comment] " Cornelia Huck
2023-03-22 16:23 ` [virtio-comment] " Parav Pandit
2023-03-22 16:36 ` Cornelia Huck
2023-03-22 16:40 ` Parav Pandit
2023-03-22 16:44 ` Cornelia Huck
2023-03-22 16:46 ` Parav Pandit [this message]
2023-03-22 16:50 ` Michael S. Tsirkin
2023-03-22 16:46 ` Michael S. Tsirkin
2023-03-22 16:49 ` Parav Pandit
2023-03-22 16:53 ` Michael S. Tsirkin
2023-03-22 17:02 ` Parav Pandit
2023-03-23 2:26 ` [virtio-comment] Re: [virtio-dev] " 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=PH0PR12MB5481F9FF6580D1F8847B9D3BDC869@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=alvaro.karsz@solid-run.com \
--cc=cohuck@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=hengqi@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.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).