From: "Michael S. Tsirkin" <mst@redhat.com>
To: Vamsi Krishna Attunuru <vattunuru@marvell.com>
Cc: Lege Wang <lege.wang@jaguarmicro.com>,
Jason Wang <jasowang@redhat.com>,
"virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
"parav@nvidia.com" <parav@nvidia.com>,
Leo Liu <leo.liu@jaguarmicro.com>,
Angus Chen <angus.chen@jaguarmicro.com>
Subject: Re: [EXTERNAL] Re: [PATCH] VIRTIO_F_USED_EVENT_AUTO_DISABLE: add new used buffer notification suppression mechanism
Date: Wed, 6 Nov 2024 02:40:36 -0500 [thread overview]
Message-ID: <20241106023956-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <MW4PR18MB52443417B7398C64244F838BA6522@MW4PR18MB5244.namprd18.prod.outlook.com>
On Tue, Nov 05, 2024 at 04:23:25PM +0000, Vamsi Krishna Attunuru wrote:
> Hi Wang, Michael, Jason,
>
> I wanted to follow up on the previous discussions regarding this new used buffer notification suppression.
>
> Since this proposal involves two changes, how about separating it out and explore the feasibilities to support interrupt coalescing with existing options.?
> 1) Support pvirtq_event_suppress/virtq_avail in PCI bar
> 2) Support used buffer notification coalescing
>
> Regards
> Vamsi
Indeed, since there's a lot of controversy, splitting the changes up
might help move this forward.
prev parent reply other threads:[~2024-11-06 7:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 3:44 [PATCH] VIRTIO_F_USED_EVENT_AUTO_DISABLE: add new used buffer notification suppression mechanism Xiaoguang Wang
2024-07-01 8:24 ` Lege Wang
2024-07-02 1:15 ` Xuan Zhuo
2024-07-02 5:30 ` [EXTERNAL] " Vamsi Krishna Attunuru
2024-07-02 7:40 ` Jason Wang
2024-07-03 4:32 ` Lege Wang
2024-07-03 5:10 ` Jason Wang
2024-07-03 7:37 ` Lege Wang
2024-07-03 7:59 ` Jason Wang
2024-07-03 8:36 ` Michael S. Tsirkin
2024-07-03 8:47 ` Jason Wang
2024-07-03 9:08 ` Michael S. Tsirkin
2024-07-04 5:37 ` Jason Wang
2024-07-04 8:30 ` Michael S. Tsirkin
2024-07-05 5:48 ` Jason Wang
2024-07-05 7:48 ` Michael S. Tsirkin
2024-07-08 1:39 ` Jason Wang
2024-07-02 12:00 ` Michael S. Tsirkin
2024-07-03 6:52 ` Lege Wang
2024-07-03 8:28 ` Michael S. Tsirkin
2024-07-03 12:14 ` Lege Wang
2024-07-03 12:34 ` Michael S. Tsirkin
2024-07-04 2:27 ` Lege Wang
2024-07-05 7:57 ` Michael S. Tsirkin
2024-07-05 11:12 ` Lege Wang
2024-07-05 11:29 ` Michael S. Tsirkin
2024-07-05 3:35 ` Lege Wang
2024-07-05 4:42 ` Parav Pandit
2024-07-05 7:52 ` Michael S. Tsirkin
2024-07-08 2:37 ` Parav Pandit
2024-07-05 8:25 ` Michael S. Tsirkin
2024-07-08 2:33 ` Parav Pandit
2024-07-05 8:00 ` Michael S. Tsirkin
2024-11-05 16:23 ` [EXTERNAL] " Vamsi Krishna Attunuru
2024-11-06 4:33 ` Jason Wang
2024-11-06 11:11 ` Vamsi Krishna Attunuru
2024-11-06 7:40 ` Michael S. Tsirkin [this message]
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=20241106023956-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=angus.chen@jaguarmicro.com \
--cc=jasowang@redhat.com \
--cc=lege.wang@jaguarmicro.com \
--cc=leo.liu@jaguarmicro.com \
--cc=ndabilpuram@marvell.com \
--cc=parav@nvidia.com \
--cc=vattunuru@marvell.com \
--cc=virtio-comment@lists.linux.dev \
/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