From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>,
"virtio@lists.oasis-open.org" <virtio@lists.oasis-open.org>
Subject: Re: [virtio-comment] [PATCH requirements 4/7] net-features: Add notification coalescing requirements
Date: Tue, 6 Jun 2023 19:06:06 -0400 [thread overview]
Message-ID: <20230606190338-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB5481C5A0E642F63B8624DBCBDC52A@PH0PR12MB5481.namprd12.prod.outlook.com>
On Tue, Jun 06, 2023 at 10:46:53PM +0000, Parav Pandit wrote:
>
>
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Tuesday, June 6, 2023 6:37 PM
>
> > > # 3. Requirements
> > > ## 3.1 Device counters
> > > @@ -143,3 +144,10 @@ struct vnet_rx_completion { 7. The device should
> > > be able to indicate when a full page buffer is consumed,
> > > which can be recycled by the driver when the packets from the completed
> > > page is fully consumed.
> > > +
> > > +## 3.3 Virtqueue notification coalescing re-enable support 1. Tx and
> > > +Rx virtqueue notification coalescing should auto-disable on
> > > + notification reporting to the driver. The driver should be able to enable
> > > + coalescing after processing the packets per VQ. This ensures that when
> > > + networking stack decides to poll, no new notifications are generated when
> > > + per VQ notification coalescing is used.
> >
> > I don't know what does auto-disable and enable coalescing mean.
> > Does this refer to VIRTIO_NET_F_NOTF_COAL?
>
> > what is the problem this is trying to solve?
> >
> Current driver when uses F_VQ_NOTF_COAL, and polling, it still receives the event (interrupt) from the device, because the time is always running.
> (event is not auto disabled on generation of the event).
> So number of interrupts are not fully controlled yet by the driver.
could we please speak virtio terms? you are not new in this area..
so this is asking for a way to disable used buffer notifications?
we actually have this with packet vq always and with split
without EVENT_IDX. what is missing?
--
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/
next prev parent reply other threads:[~2023-06-06 23:06 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 22:02 [virtio-comment] [PATCH requirements 0/7] virtio net new features requirements Parav Pandit
2023-06-01 22:02 ` [virtio-comment] [PATCH requirements 1/7] net-features: Add requirements document for release 1.4 Parav Pandit
2023-06-06 22:15 ` Michael S. Tsirkin
2023-06-06 22:28 ` Parav Pandit
2023-06-06 22:56 ` Michael S. Tsirkin
2023-06-06 23:08 ` Parav Pandit
2023-06-06 23:18 ` Michael S. Tsirkin
2023-06-07 9:03 ` [virtio-comment] Re: [virtio] " Xuan Zhuo
2023-06-07 20:35 ` Michael S. Tsirkin
2023-06-07 20:39 ` Parav Pandit
2023-06-07 20:50 ` Michael S. Tsirkin
2023-06-07 20:53 ` Parav Pandit
2023-06-07 9:31 ` Xuan Zhuo
2023-06-01 22:03 ` [virtio-comment] [PATCH requirements 2/7] net-features: Add low latency transmit queue requirements Parav Pandit
2023-06-06 22:25 ` Michael S. Tsirkin
2023-06-06 22:35 ` Parav Pandit
2023-06-01 22:03 ` [virtio-comment] [PATCH requirements 3/7] net-features: Add low latency receive " Parav Pandit
2023-06-06 22:33 ` Michael S. Tsirkin
2023-06-06 22:44 ` Parav Pandit
2023-06-06 23:03 ` Michael S. Tsirkin
2023-06-01 22:03 ` [virtio-comment] [PATCH requirements 4/7] net-features: Add notification coalescing requirements Parav Pandit
2023-06-06 22:36 ` Michael S. Tsirkin
2023-06-06 22:46 ` Parav Pandit
2023-06-06 23:06 ` Michael S. Tsirkin [this message]
2023-06-01 22:03 ` [virtio-comment] [PATCH requirements 5/7] net-features: Add n-tuple receive flow steering requirements Parav Pandit
2023-06-02 3:35 ` Heng Qi
2023-06-02 3:51 ` Parav Pandit
2023-06-02 4:39 ` [virtio-comment] Re: [virtio] " Heng Qi
2023-06-06 12:08 ` Heng Qi
2023-06-06 21:49 ` [virtio-comment] " Parav Pandit
2023-06-12 14:35 ` [virtio-comment] " Heng Qi
2023-06-12 17:26 ` [virtio-comment] " Parav Pandit
2023-06-13 2:28 ` Heng Qi
2023-06-13 8:57 ` [virtio-comment] " Michael S. Tsirkin
2023-06-13 9:16 ` Cornelia Huck
2023-06-13 11:33 ` [virtio-comment] " Parav Pandit
2023-06-07 2:47 ` Jason Wang
2023-06-07 3:22 ` Parav Pandit
2023-06-13 2:57 ` [virtio-comment] Re: [virtio] " Heng Qi
2023-06-13 4:16 ` [virtio-comment] " Parav Pandit
2023-06-13 5:04 ` [virtio-comment] " Heng Qi
2023-06-13 12:24 ` [virtio-comment] " Parav Pandit
2023-06-14 3:43 ` [virtio-comment] " Heng Qi
2023-06-14 3:48 ` [virtio-comment] " Parav Pandit
2023-06-14 3:53 ` Heng Qi
2023-06-01 22:03 ` [virtio-comment] [PATCH requirements 6/7] net-features: Add packet timestamp requirements Parav Pandit
2023-06-06 22:40 ` Michael S. Tsirkin
2023-06-06 22:51 ` Parav Pandit
2023-06-06 23:08 ` Michael S. Tsirkin
2023-06-01 22:03 ` [virtio-comment] [PATCH requirements 7/7] net-features: Add header data split requirements Parav Pandit
2023-06-06 22:41 ` Michael S. Tsirkin
2023-06-08 14:57 ` Parav Pandit
2023-06-02 3:06 ` [virtio-comment] Re: [virtio] [PATCH requirements 0/7] virtio net new features requirements Heng Qi
2023-06-06 22:49 ` [virtio-comment] " Michael S. Tsirkin
2023-06-06 22:56 ` Parav Pandit
2023-06-06 23:10 ` Michael S. Tsirkin
2023-06-07 2:49 ` Jason Wang
2023-06-07 3:33 ` Parav Pandit
-- strict thread matches above, loose matches on Subject: below --
2023-07-24 3:34 Parav Pandit
2023-07-24 3:34 ` [virtio-comment] [PATCH requirements 4/7] net-features: Add notification coalescing requirements Parav Pandit
2023-08-14 11:57 ` David Edmondson
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=20230606190338-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@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