From: Tiwei Bie <tiwei.bie@intel.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: mst@redhat.com, pbonzini@redhat.com, jasowang@redhat.com,
virtio-dev@lists.oasis-open.org, dan.daly@intel.com,
cunming.liang@intel.com, zhihong.wang@intel.com
Subject: Re: [virtio-dev] [PATCH v3] VIRTIO_F_IO_BARRIER: use I/O barriers in driver
Date: Tue, 15 May 2018 18:23:47 +0800 [thread overview]
Message-ID: <20180515102347.GA10528@debian> (raw)
In-Reply-To: <20180515094044.GG14755@stefanha-x1.localdomain>
On Tue, May 15, 2018 at 10:40:44AM +0100, Stefan Hajnoczi wrote:
> On Thu, May 10, 2018 at 11:41:26PM +0800, Tiwei Bie wrote:
> > There will be hardware virtio devices in the future, which
> > require drivers to use the barriers suitable for I/O devices,
> > compared with software virtio devices which just require
> > drivers to use the barriers suitable for CPU cores.
> >
> > To fix the ordering issue for hardware virtio devices, add
> > a new feature: VIRTIO_F_IO_BARRIER. When negotiated, driver
> > will use the barriers suitable for I/O devices.
> >
> > Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
> > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> > ---
> > v2 -> v3:
> > - Update the feature bits allocation (Stefan);
> >
> > v1 -> v2:
> > - Rebase to the latest spec (MST);
> > - Use a smaller textwidth (according to _vimrc);
> >
> > RFC -> v1:
> > - Use plural (Stefan);
> > - Add more details (Stefan);
> >
> > content.tex | 20 ++++++++++++++++++--
> > 1 file changed, 18 insertions(+), 2 deletions(-)
>
> Thanks for your patience!
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
It's my pleasure. Thanks for your review! :)
Best regards,
Tiwei Bie
---------------------------------------------------------------------
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:[~2018-05-15 10:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 15:41 [virtio-dev] [PATCH v3] VIRTIO_F_IO_BARRIER: use I/O barriers in driver Tiwei Bie
2018-05-15 9:40 ` Stefan Hajnoczi
2018-05-15 10:23 ` Tiwei Bie [this message]
2018-05-15 12:39 ` [virtio-dev] " Michael S. Tsirkin
2018-05-16 1:19 ` Tiwei Bie
2018-06-14 0:24 ` Michael S. Tsirkin
2018-06-14 3:30 ` Jason Wang
2018-05-16 1:38 ` [virtio-dev] " Tiwei Bie
2018-06-20 3:31 ` Michael S. Tsirkin
2018-06-20 13:40 ` Tiwei Bie
2018-06-20 14:02 ` Michael S. Tsirkin
2018-06-20 14:31 ` Tiwei Bie
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=20180515102347.GA10528@debian \
--to=tiwei.bie@intel.com \
--cc=cunming.liang@intel.com \
--cc=dan.daly@intel.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-dev@lists.oasis-open.org \
--cc=zhihong.wang@intel.com \
/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.