From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org,
Tiwei Bie <tiwei.bie@intel.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Dhanoa, Kully" <kully.dhanoa@intel.com>
Subject: [virtio] Re: [virtio-dev] Re: [virtio] [PATCH v12] VIRTIO_F_NOTIFICATION_DATA: extra data to devices
Date: Tue, 3 Apr 2018 16:32:53 +0200 [thread overview]
Message-ID: <20180403163253.29d207d3.cohuck@redhat.com> (raw)
In-Reply-To: <28a35397-b62a-0c5d-ad77-c8a6f308dd5f@linux.vnet.ibm.com>
On Mon, 2 Apr 2018 17:34:50 +0200
Halil Pasic <pasic@linux.vnet.ibm.com> wrote:
> On 03/29/2018 04:30 PM, Michael S. Tsirkin wrote:
> > On Thu, Mar 29, 2018 at 04:15:19PM +0200, Halil Pasic wrote:
> >>
> [..]
> >>
> >> I don't have a good solution, otherwise I would have proposed already.
> >> Maybe something like 'available notification' and 'used notification' is
> >> worth considering. I don't like that one can read available and used
> >> as normal English (that is a notification that is available and not
> >> a notification that buffers were made available at the given virtqueue).
> >
> > I think I like this.
> >
> > Available buffer / used buffer notifications?
> >
>
> I will do it!
> @Connie: if you have concerns or something even better in mind
> please do tell.
No further comments from me.
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
next prev parent reply other threads:[~2018-04-03 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 16:37 [virtio] [PATCH v12] VIRTIO_F_NOTIFICATION_DATA: extra data to devices Michael S. Tsirkin
2018-03-28 16:56 ` Halil Pasic
2018-03-28 17:21 ` Michael S. Tsirkin
2018-03-29 9:05 ` Cornelia Huck
2018-03-29 12:52 ` Michael S. Tsirkin
2018-03-29 13:04 ` Cornelia Huck
2018-03-29 13:10 ` Michael S. Tsirkin
2018-03-29 14:15 ` Halil Pasic
2018-03-29 14:30 ` Michael S. Tsirkin
2018-04-02 15:34 ` [virtio] Re: [virtio-dev] " Halil Pasic
2018-04-03 14:32 ` Cornelia Huck [this message]
2018-03-28 22:30 ` [virtio] on spec clarifications Michael S. Tsirkin
2018-04-03 0:11 ` Halil Pasic
2018-04-08 20:57 ` Halil Pasic
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=20180403163253.29d207d3.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=kully.dhanoa@intel.com \
--cc=mst@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=stefanha@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=virtio-dev@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