qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [RFC 0/7] dataplane: switch to N:M devices-per-thread model
Date: Thu, 12 Dec 2013 14:19:37 +0100	[thread overview]
Message-ID: <1386854384-1992-1-git-send-email-stefanha@redhat.com> (raw)

This series moves the event loop thread out of dataplane code.  It makes
-iothread id=foo a separate concept.  This makes it possible to bind several
devices to the same iothread.

Syntax:

  qemu -iothread id=iothread0 \
       -device virtio-blk-pci,iothread=iothread0,x-data-plane=on,...

For backwards-compatibility the iothread= parameter can be omitted.  A
per-device IOThread will be created behind the scenes (just like the old 1:1
threading model).

This series includes the aio_context_acquire/release API which makes it easy to
synchronize access to AioContext across threads.

The IOThread object is really a stand-in for Michael Roth's QContext.  They
both have the same purpose but I needed something to develop against while
QContext is unfinished.  In order to make progress I'd like to agree on the
user-visible API that IOThread/QContext presents.  That way QContext can be
implemented step-by-step without holding up dataplane.

Finally, the -iothread command-line option will soon be replaced with -object.
I am following Igor's work in the area and will try to help get that code in.

Stefan Hajnoczi (7):
  rfifolock: add recursive FIFO lock
  aio: add aio_context_acquire() and aio_context_release()
  iothread: add I/O thread object
  iothread: command-line option
  qdev: add get_pointer_and_free() for temporary strings
  iothread: add "iothread" qdev property type
  dataplane: replace internal thread with IOThread

 Makefile.objs                    |   1 +
 async.c                          |  18 +++++
 hw/block/dataplane/virtio-blk.c  |  91 ++++++++++++-----------
 hw/core/qdev-properties-system.c |  65 +++++++++++++++++
 include/block/aio.h              |  18 +++++
 include/hw/qdev-properties.h     |   3 +
 include/hw/virtio/virtio-blk.h   |   8 ++-
 include/qemu/rfifolock.h         |  54 ++++++++++++++
 include/sysemu/iothread.h        |  32 +++++++++
 include/sysemu/sysemu.h          |   1 +
 iothread.c                       | 152 +++++++++++++++++++++++++++++++++++++++
 qemu-options.hx                  |   8 +++
 tests/Makefile                   |   2 +
 tests/test-aio.c                 |  58 +++++++++++++++
 tests/test-rfifolock.c           |  90 +++++++++++++++++++++++
 util/Makefile.objs               |   1 +
 util/rfifolock.c                 |  78 ++++++++++++++++++++
 vl.c                             |  12 ++++
 18 files changed, 647 insertions(+), 45 deletions(-)
 create mode 100644 include/qemu/rfifolock.h
 create mode 100644 include/sysemu/iothread.h
 create mode 100644 iothread.c
 create mode 100644 tests/test-rfifolock.c
 create mode 100644 util/rfifolock.c

-- 
1.8.4.2

             reply	other threads:[~2013-12-12 13:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 13:19 Stefan Hajnoczi [this message]
2013-12-12 13:19 ` [Qemu-devel] [RFC 1/7] rfifolock: add recursive FIFO lock Stefan Hajnoczi
2013-12-12 13:19 ` [Qemu-devel] [RFC 2/7] aio: add aio_context_acquire() and aio_context_release() Stefan Hajnoczi
2013-12-12 13:19 ` [Qemu-devel] [RFC 3/7] iothread: add I/O thread object Stefan Hajnoczi
2013-12-12 18:00   ` Michael Roth
2013-12-13  9:20     ` Stefan Hajnoczi
2013-12-12 13:19 ` [Qemu-devel] [RFC 4/7] iothread: command-line option Stefan Hajnoczi
2013-12-12 13:19 ` [Qemu-devel] [RFC 5/7] qdev: add get_pointer_and_free() for temporary strings Stefan Hajnoczi
2013-12-12 13:19 ` [Qemu-devel] [RFC 6/7] iothread: add "iothread" qdev property type Stefan Hajnoczi
2013-12-12 13:19 ` [Qemu-devel] [RFC 7/7] dataplane: replace internal thread with IOThread Stefan Hajnoczi

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=1386854384-1992-1-git-send-email-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).