Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>
Cc: Parav Pandit <parav@nvidia.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: [virtio-comment] Re: [virtio-dev] [PATCH v2] virtio_net: support low and high rate of notification coalescing
Date: Tue, 17 Jan 2023 10:18:41 -0500	[thread overview]
Message-ID: <20230117101430-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJs=3_At3KQ0DvZ6P3bpZBvh9H3L5HHMeO-zq594dFG+MHA=bg@mail.gmail.com>

On Tue, Jan 17, 2023 at 03:03:43PM +0200, Alvaro Karsz wrote:
> > By comparison this patch is an attempt to offload ethtool's
> > --coalesce parameters to the card. IMO what it misses is
> > completeness, e.g. sample-interval is not specified.
> 
> AFAIK sample-interval refers to the adaptive coalescing
> (adaptive-rx/adaptive-tx) and not to high/low.
> 
> include/uapi/linux/ethtool.h:
>  * @rate_sample_interval: How often to do adaptive coalescing packet rate
>  * sampling, measured in seconds.  Must not be zero.

Oh you are right. So sampling interval here is arbitrary,
defined by the device. Worth documenting.

> > Also, introspection is missing and it's useful to avoid
> > keeping all state in the driver.
> 
> I don't get it, can you please elaborate?

I mean --show-coalesce

-- 
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-01-17 15:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11 15:21 [virtio-dev] [PATCH v2] virtio_net: support low and high rate of notification coalescing Alvaro Karsz
2023-01-11 18:21 ` [virtio-dev] " Alvaro Karsz
2023-01-16 14:32   ` Alvaro Karsz
2023-01-16 16:01     ` [virtio-comment] " Michael S. Tsirkin
2023-01-16 15:59 ` [virtio-dev] " Michael S. Tsirkin
2023-01-17 12:42   ` [virtio-comment] " Alvaro Karsz
2023-01-16 19:42 ` [virtio-dev] " Parav Pandit
2023-01-16 20:33   ` Michael S. Tsirkin
2023-01-16 20:52     ` [virtio-comment] " Parav Pandit
2023-01-16 21:30       ` Michael S. Tsirkin
2023-01-17  0:07         ` [virtio-comment] " Parav Pandit
2023-01-17  0:27           ` Michael S. Tsirkin
2023-01-17  3:49             ` [virtio-comment] " Parav Pandit
2023-01-17 13:03         ` [virtio-comment] " Alvaro Karsz
2023-01-17 15:18           ` Michael S. Tsirkin [this message]
2023-02-06  8:10             ` Alvaro Karsz
2023-01-17 12:44   ` 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=20230117101430-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