From: "Michael S. Tsirkin" <mst@redhat.com>
To: rusty@rustcorp.com.au, virtualization@lists.linux-foundation.org
Subject: [PATCH 0/6] virtio: virtqueue ops cleanup
Date: Mon, 12 Apr 2010 16:18:19 +0300 [thread overview]
Message-ID: <cover.1271078235.git.mst@redhat.com> (raw)
virtqueue ops were introduced in the hope that we'll
have multiple implementations besides virtio_ring,
but none have surfaced so far, and given that
existing virtio ring is deployed in production
we are likely stuck with it now, so this layer just
adds complexity and overhead.
Further, the need to pass vq twice to each call
(as in dev->vq->vq_ops->kick(dev->vq) ) adds potential
for cut and paste errors.
This patchset does the following:
- add inline wrappers converting the above to virtqueue_kick(dev->vq)
- convert all users to this API
- remove vq_ops indirection, implementing virtqueue_xx directly
in virtio_ring
Note that if we ever want to add another vring implementation,
we'll only need to revert the last patch in the series,
devices won't have to change.
--
MST
Michael S. Tsirkin (6):
virtio: add virtqueue_ vq_ops wrappers
virtio_balloon: use virtqueue_xxx wrappers
virtio_console: use virtqueue_xxx wrappers
virtio_blk: use virtqueue_xxx wrappers
virtio_net: use virtqueue_xxx wrappers
virtio_ring: remove a level of indirection
drivers/block/virtio_blk.c | 6 ++--
drivers/char/virtio_console.c | 32 +++++++++++++-------------
drivers/net/virtio_net.c | 46 +++++++++++++++++++-------------------
drivers/virtio/virtio_balloon.c | 17 ++++++-------
drivers/virtio/virtio_ring.c | 36 +++++++++++++-----------------
include/linux/virtio.h | 43 +++++++++++++++++------------------
6 files changed, 87 insertions(+), 93 deletions(-)
next reply other threads:[~2010-04-12 13:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 13:18 Michael S. Tsirkin [this message]
2010-04-12 13:18 ` [PATCH 1/6] virtio: add virtqueue_ vq_ops wrappers Michael S. Tsirkin
2010-04-12 13:18 ` [PATCH 2/6] virtio_balloon: use virtqueue_xxx wrappers Michael S. Tsirkin
2010-04-12 13:18 ` [PATCH 3/6] virtio_console: " Michael S. Tsirkin
2010-04-12 13:18 ` [PATCH 4/6] virtio_blk: " Michael S. Tsirkin
2010-04-12 13:19 ` [PATCH 5/6] virtio_net: " Michael S. Tsirkin
2010-04-12 13:19 ` [PATCH 6/6] virtio_ring: remove a level of indirection Michael S. Tsirkin
2010-04-13 13:06 ` [PATCH 0/6] virtio: virtqueue ops cleanup Michael S. Tsirkin
2010-04-13 13:11 ` [PATCH] virtio-rng: use virtqueue_xxx wrappers Michael S. Tsirkin
2010-04-13 13:11 ` [PATCH] trans_virtio: " Michael S. Tsirkin
2010-04-20 9:10 ` Rusty Russell
2010-04-19 20:49 ` [PATCH 0/6] virtio: virtqueue ops cleanup Michael S. Tsirkin
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=cover.1271078235.git.mst@redhat.com \
--to=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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).