qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Blue Swirl <blauwirbel@gmail.com>, Khoa Huynh <khoa@us.ibm.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>, Asias He <asias@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 00/11] virtio: virtio-blk data plane
Date: Thu, 29 Nov 2012 17:19:46 +0200	[thread overview]
Message-ID: <20121129151946.GD10896@redhat.com> (raw)
In-Reply-To: <20121129144804.GC14196@stefanha-thinkpad.redhat.com>

On Thu, Nov 29, 2012 at 03:48:04PM +0100, Stefan Hajnoczi wrote:
> On Thu, Nov 29, 2012 at 04:09:28PM +0200, Michael S. Tsirkin wrote:
> > On Thu, Nov 29, 2012 at 10:18:59AM +0100, Stefan Hajnoczi wrote:
> > > Michael, Paolo: Are you happy with v4?
> > 
> > Looks pretty clean by itself. I sent some comments but they can be
> > addressed later.  What worries me most is the code duplication with
> > regular virtio.
> > 
> > I see two ways to reduce the maintainance somewhat
> > - split out ring handling code in virtio-blk
> >   to a separate file to make it more obvious which part
> >   is inactive when data plane runs.
> > - share ring processing code with virtio/virtio-blk
> >   (e.g. use callbacks)
> > 
> > Was any thought given to implementing one of these two
> > approaches? 
> 
> Yes, your option #2 is where I'd like to move once threaded memory
> dispatch is working.  I hope we can run virtio.c code in a thread
> outside the global mutex soon.  That way we can kill
> hw/dataplane/vring.[ch].
> 
> Ping Fan Liu has been working on the memory API and device emulation
> stuff that we need in order to eventually use virtio.c outside the
> global mutex.
> 
> Stefan

I guess we can live with this short term.

      reply	other threads:[~2012-11-29 15:28 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22 15:16 [Qemu-devel] [PATCH v4 00/11] virtio: virtio-blk data plane Stefan Hajnoczi
2012-11-22 15:16 ` [Qemu-devel] [PATCH v4 01/11] raw-posix: add raw_get_aio_fd() for virtio-blk-data-plane Stefan Hajnoczi
2012-11-22 15:16 ` [Qemu-devel] [PATCH v4 02/11] configure: add CONFIG_VIRTIO_BLK_DATA_PLANE Stefan Hajnoczi
2012-11-22 15:16 ` [Qemu-devel] [PATCH v4 03/11] dataplane: add host memory mapping code Stefan Hajnoczi
2012-11-29 12:33   ` Michael S. Tsirkin
2012-11-29 12:45     ` Stefan Hajnoczi
2012-11-29 12:54       ` Michael S. Tsirkin
2012-11-29 12:57         ` Michael S. Tsirkin
2012-12-05  8:13           ` Stefan Hajnoczi
2012-11-29 13:54   ` Michael S. Tsirkin
2012-11-29 14:26     ` Stefan Hajnoczi
2012-11-29 14:36       ` Michael S. Tsirkin
2012-11-29 15:26         ` Paolo Bonzini
2012-12-05  8:31         ` Stefan Hajnoczi
2012-12-05 11:22           ` Michael S. Tsirkin
2012-11-22 15:16 ` [Qemu-devel] [PATCH v4 04/11] dataplane: add virtqueue vring code Stefan Hajnoczi
2012-11-29 12:50   ` Michael S. Tsirkin
2012-11-29 15:17     ` Paolo Bonzini
2012-12-05 12:57     ` Stefan Hajnoczi
2012-11-29 13:48   ` Michael S. Tsirkin
2012-11-22 15:16 ` [Qemu-devel] [PATCH v4 05/11] dataplane: add event loop Stefan Hajnoczi
2012-11-22 15:16 ` [Qemu-devel] [PATCH v4 06/11] dataplane: add Linux AIO request queue Stefan Hajnoczi
2012-11-22 15:16 ` [Qemu-devel] [PATCH v4 07/11] iov: add iov_discard() to remove data Stefan Hajnoczi
2012-11-22 15:16 ` [Qemu-devel] [PATCH v4 08/11] test-iov: add iov_discard() testcase Stefan Hajnoczi
2012-11-22 15:16 ` [Qemu-devel] [PATCH v4 09/11] iov: add qemu_iovec_concat_iov() Stefan Hajnoczi
2012-11-22 15:16 ` [Qemu-devel] [PATCH v4 10/11] dataplane: add virtio-blk data plane code Stefan Hajnoczi
2012-11-29 13:41   ` Michael S. Tsirkin
2012-11-29 14:02   ` Michael S. Tsirkin
2012-11-29 15:21     ` Paolo Bonzini
2012-11-29 15:27       ` Michael S. Tsirkin
2012-11-29 15:47         ` Paolo Bonzini
2012-11-30 13:57           ` Stefan Hajnoczi
2012-11-22 15:16 ` [Qemu-devel] [PATCH v4 11/11] virtio-blk: add x-data-plane=on|off performance feature Stefan Hajnoczi
2012-11-29 13:12   ` Michael S. Tsirkin
2012-11-29 14:45     ` Stefan Hajnoczi
2012-11-29 14:55       ` Michael S. Tsirkin
2012-12-04 11:20         ` Michael S. Tsirkin
2012-12-04 14:19           ` Stefan Hajnoczi
2012-11-29  9:18 ` [Qemu-devel] [PATCH v4 00/11] virtio: virtio-blk data plane Stefan Hajnoczi
2012-11-29 12:03   ` Paolo Bonzini
2012-11-29 14:09   ` Michael S. Tsirkin
2012-11-29 14:48     ` Stefan Hajnoczi
2012-11-29 15:19       ` 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=20121129151946.GD10896@redhat.com \
    --to=mst@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=asias@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=khoa@us.ibm.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).