From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>
Cc: Heng Qi <hengqi@linux.alibaba.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, jasowang@redhat.com,
parav@nvidia.com, david.edmondson@oracle.com
Subject: [virtio-dev] Re: [virtio-comment] Re: [PATCH v4] virtio-net: Fix and update VIRTIO_NET_F_NOTF_COAL feature
Date: Thu, 16 Feb 2023 06:44:28 -0500 [thread overview]
Message-ID: <20230216064301-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJs=3_DbSMTM=AmWqXAAE82Sa_JSJHzS=tss_UxsOFmc57HN6Q@mail.gmail.com>
On Thu, Feb 16, 2023 at 10:40:10AM +0200, Alvaro Karsz wrote:
> Hi Heng,
>
> > > +When the device has non-zero \field{usecs} and non-zero \field{max_packets}, it starts counting usecs and packets upon receiving/sending a packet.
> > > +The device counts packets and usecs for each receive virtqueue and transmit virtqueue separately.
> > > +In this case, the notification conditions are met when \field{usecs} usecs elapses, or upon sending/receiving \field{max_packets} packets, whichever happens first.
> > > +
> >
> > Hi, Alvaro.
> >
> > "when \field{usecs} usecs elapses" --> "when \field{usecs} elapses", right?
>
> Actually, no.
> \field{usecs} refers to the field in the struct.
> usecs refers to the units of measurement.
>
> So if for example \field{usecs} = 40, then it evaluates to 40 usecs ->
> "are met when 40 usecs elapses".
But this is not how it reads, people are not computers, and in the
compiled PDF \field{usec} just looks as usecs in italics.
> I can change the field name in the struct to "max_usecs" if people
> think it's necessary.
Maybe that's a good idea.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-02-16 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 7:32 [virtio-dev] [PATCH v4] virtio-net: Fix and update VIRTIO_NET_F_NOTF_COAL feature Alvaro Karsz
2023-02-16 8:28 ` [virtio-comment] " Heng Qi
2023-02-16 8:40 ` Alvaro Karsz
2023-02-16 11:44 ` Michael S. Tsirkin [this message]
2023-02-16 11:52 ` 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=20230216064301-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=david.edmondson@oracle.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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.