Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Alvaro Karsz <alvaro.karsz@solid-run.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>,
	"jasowang@redhat.com" <jasowang@redhat.com>
Subject: Re: [virtio-comment] RE: [virtio-dev] [PATCH] virtio-net: Fix and update VIRTIO_NET_F_NOTF_COAL feature
Date: Wed, 8 Feb 2023 12:38:41 -0500	[thread overview]
Message-ID: <20230208123630-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481BBF4B010D1B197DEF27FDCD89@PH0PR12MB5481.namprd12.prod.outlook.com>

On Wed, Feb 08, 2023 at 05:30:28PM +0000, Parav Pandit wrote:
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Tuesday, February 7, 2023 9:18 AM
> 
> > > Why migration generate too many spurious interrupts?
> > 
> > Because, you might want to migrate from hardware with to hardware without
> > coalescing features. So you just tell guest "sure I will coalesce" but in fact send
> > interrupts normally.
> 
> For the hardware that has fake coalescing, HV wouldn't know it anyway without doing pre verification.
> And HV may not migrate in such case for best experience.
> HV may choose to migrate with low accuracy as you say, which is fine.
> 
> But the spec guidance for the device implementations is to promote some reasonable level of accuracy.
> Hard to define in words here.
> Best effort is wide spectrum of range. :)
> 
> Typically, we say in the spec as SHOULD. 
> So, lets skip the best-effort wording and stick to SHOULD part like rest of the spec.

I think the point of best-effort is that driver must handle interrupts
that arrive earlier. This is how we used it elsewhere. What else does
it include in your opinion that we absolutely must exclude?
I feel it's a good fit for a non-conformance section which is
by nature a bit informal.

For a conformance section SHOULD is indeed a good fit.

-- 
MST


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/


  reply	other threads:[~2023-02-08 17:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06  8:47 [virtio-dev] [PATCH] virtio-net: Fix and update VIRTIO_NET_F_NOTF_COAL feature Alvaro Karsz
2023-02-06 19:13 ` [virtio-comment] " Parav Pandit
2023-02-06 21:08   ` Michael S. Tsirkin
2023-02-06 21:53     ` [virtio-comment] " Parav Pandit
2023-02-06 22:26       ` Michael S. Tsirkin
2023-02-06 23:08         ` [virtio-comment] " Parav Pandit
2023-02-07 14:18           ` [virtio-dev] " Michael S. Tsirkin
2023-02-08 10:41             ` Alvaro Karsz
2023-02-08 17:30             ` Parav Pandit
2023-02-08 17:38               ` Michael S. Tsirkin [this message]
2023-02-08 17:48                 ` Parav Pandit
2023-02-08 18:11                   ` Alvaro Karsz
2023-02-07  0:33       ` Heng Qi
2023-02-07  0:40         ` Parav Pandit
2023-02-07 10:05   ` [virtio-comment] " Alvaro Karsz

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=20230208123630-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alvaro.karsz@solid-run.com \
    --cc=jasowang@redhat.com \
    --cc=parav@nvidia.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.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