From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Vamsi Krishna Attunuru <vattunuru@marvell.com>,
"lege.wang@jaguarmicro.com" <lege.wang@jaguarmicro.com>,
"virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>,
Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>
Subject: Re: [virtio-comment] [RFC PATCH] VIRTIO_F_USED_EVENT_AUTO_DISABLE: add new used buffer notification suppression mechanism
Date: Thu, 20 Jun 2024 02:49:47 -0400 [thread overview]
Message-ID: <20240620024922-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54810AA98716C6398A412342DCCF2@PH0PR12MB5481.namprd12.prod.outlook.com>
On Wed, Jun 19, 2024 at 06:08:28PM +0000, Parav Pandit wrote:
>
> > From: Vamsi Krishna Attunuru <vattunuru@marvell.com>
> > Sent: Wednesday, June 19, 2024 8:49 PM
> >
> > Hi Lege.wang
> >
> > Thank you for proposing this new feature. This capability is very much useful
> > with PCI transport on newer hardwares.
> >
> > May I know the current status of this proposal, is V1 already planned and
> > prepared for the review.?, I would like to collaborate on refining the proposal
> > and the required changes in the spec.
> >
> > Regards
> > Vamsi
> >
> >
> >
> Removed old dead mailing list.
> Added the recent mailing list.
Yes - pls subscribe and repost to the new list. Most people saw nothing.
Thanks!
--
MST
next prev parent reply other threads:[~2024-06-20 6:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MW4PR18MB52448CB41784611E654333B3A6CF2@MW4PR18MB5244.namprd18.prod.outlook.com>
2024-06-19 18:08 ` [virtio-comment] [RFC PATCH] VIRTIO_F_USED_EVENT_AUTO_DISABLE: add new used buffer notification suppression mechanism Parav Pandit
2024-06-20 6:49 ` Michael S. Tsirkin [this message]
2024-06-20 14:08 Vamsi Krishna Attunuru
[not found] ` <SI2PR06MB5385B62E9EB693F64A3FB613FFD42@SI2PR06MB5385.apcprd06.prod.outlook.com>
2024-06-27 4:27 ` Vamsi Krishna Attunuru
-- strict thread matches above, loose matches on Subject: below --
2024-01-25 2:30 Xiaoguang Wang
2024-01-25 3:28 ` Lege Wang
2024-01-30 6:11 ` Lege Wang
2024-01-30 6:52 ` Parav Pandit
2024-01-31 6:33 ` Lege Wang
2024-01-31 6:45 ` Parav Pandit
2024-01-31 7:21 ` Lege Wang
2024-01-31 7:24 ` Parav Pandit
2024-01-31 8:39 ` Lege Wang
2024-02-01 9:44 ` Lege Wang
2024-02-05 7:40 ` Parav Pandit
2024-02-22 1:56 ` Lege Wang
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=20240620024922-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=lege.wang@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 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.