From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Ming Lei <ming.lei@canonical.com>, Fam Zheng <famz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 5/9] virtio-blk: multiqueue batch notify
Date: Fri, 27 May 2016 14:38:54 -0700 [thread overview]
Message-ID: <20160527213854.GP27946@stefanha-x1.localdomain> (raw)
In-Reply-To: <de1163ed-dd0c-f69d-35ce-e9e44b273620@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
On Sat, May 21, 2016 at 06:02:52PM +0200, Paolo Bonzini wrote:
>
>
> On 21/05/2016 01:40, Stefan Hajnoczi wrote:
> > + while ((i = find_next_bit(s->batch_notify_vqs, nvqs, i)) < nvqs) {
> > + VirtQueue *vq = virtio_get_queue(vdev, i);
> > +
> > + bitmap_clear(s->batch_notify_vqs, i, 1);
>
> clear_bit?
Ignorance on my part. Thanks!
> > + if (s->dataplane_started && !s->dataplane_disabled) {
> > + virtio_blk_data_plane_notify(s->dataplane, vq);
> > + } else {
> > + virtio_notify(vdev, vq);
> > + }
>
> The find_next_bit loop is not very efficient and could use something
> similar to commit 41074f3 ("omap_intc: convert ffs(3) to ctz32() in
> omap_inth_sir_update()", 2015-04-28). But it can be improved later.
Cool, will try that for inspiration in v2.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-05-27 21:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 23:40 [Qemu-devel] [PATCH 0/9] virtio-blk: multiqueue support Stefan Hajnoczi
2016-05-20 23:40 ` [Qemu-devel] [PATCH 1/9] virtio-blk: use batch notify in non-dataplane case Stefan Hajnoczi
2016-05-20 23:40 ` [Qemu-devel] [PATCH 2/9] virtio-blk: tell dataplane which vq to notify Stefan Hajnoczi
2016-05-20 23:40 ` [Qemu-devel] [PATCH 3/9] virtio-blk: associate request with a virtqueue Stefan Hajnoczi
2016-05-20 23:40 ` [Qemu-devel] [PATCH 4/9] virtio-blk: add VirtIOBlockConf->num_queues Stefan Hajnoczi
2016-05-20 23:40 ` [Qemu-devel] [PATCH 5/9] virtio-blk: multiqueue batch notify Stefan Hajnoczi
2016-05-21 16:02 ` Paolo Bonzini
2016-05-27 21:38 ` Stefan Hajnoczi [this message]
2016-05-23 2:43 ` Fam Zheng
2016-05-23 8:17 ` Paolo Bonzini
2016-05-23 8:56 ` Fam Zheng
2016-05-20 23:40 ` [Qemu-devel] [PATCH 6/9] vmstate: add VMSTATE_VARRAY_UINT32_ALLOC Stefan Hajnoczi
2016-05-20 23:40 ` [Qemu-devel] [PATCH 7/9] virtio-blk: live migrate s->rq with multiqueue Stefan Hajnoczi
2016-05-21 15:37 ` Paolo Bonzini
2016-05-27 21:42 ` Stefan Hajnoczi
2016-05-20 23:40 ` [Qemu-devel] [PATCH 8/9] virtio-blk: dataplane multiqueue support Stefan Hajnoczi
2016-05-20 23:40 ` [Qemu-devel] [PATCH 9/9] virtio-blk: add num-queues device property Stefan Hajnoczi
2016-05-24 12:51 ` [Qemu-devel] [PATCH 0/9] virtio-blk: multiqueue support Christian Borntraeger
2016-05-27 21:44 ` Stefan Hajnoczi
2016-05-31 0:44 ` Stefan Hajnoczi
2016-05-27 11:55 ` [Qemu-devel] [RFC] virtio-blk: simple multithreaded MQ implementation for bdrv_raw Roman Pen
2016-05-27 22:27 ` Stefan Hajnoczi
2016-05-30 6:40 ` Alexandre DERUMIER
2016-05-30 12:14 ` Roman Penyaev
2016-05-30 11:59 ` Roman Penyaev
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=20160527213854.GP27946@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=ming.lei@canonical.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).