From: Stefan Hajnoczi <stefanha@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] Linux multiqueue block layer thoughts
Date: Tue, 3 Dec 2013 15:55:12 +0100 [thread overview]
Message-ID: <20131203145512.GH24604@stefanha-thinkpad.muc.redhat.com> (raw)
In-Reply-To: <20131128021513.GJ2360@kernel.dk>
On Wed, Nov 27, 2013 at 07:15:13PM -0700, Jens Axboe wrote:
> On Wed, Nov 27 2013, Stefan Hajnoczi wrote:
> > At the end of all this we'd arrive at the following architecture:
> > 1. Guest virtio device has multiple queues (1 per node or vcpu).
> > 2. QEMU has multiple dataplane/QContext threads that process virtqueue
> > kicks, they are bound to host CPUs/nodes.
> > 3. Linux kernel has multiqueue block I/O.
>
> I think that sounds very reasonable. Let me know if there's anything you
> need help or advice with.
>
> > Jens: when experimenting with multiqueue virtio-blk, how far did you
> > modify QEMU to eliminate global request processing state from block.c?
>
> I did very little scaling testing on virtio-blk, it was more a demo case
> for conversion than anything else. So probably not of much use to what
> you are looking for...
Okay, thanks. It will be a while before the whole stack supports
multiqueue but it's good to know this approach sounds reasonable.
Stefan
prev parent reply other threads:[~2013-12-03 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 10:16 [Qemu-devel] Linux multiqueue block layer thoughts Stefan Hajnoczi
2013-11-28 2:15 ` Jens Axboe
2013-12-03 14:55 ` Stefan Hajnoczi [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=20131203145512.GH24604@stefanha-thinkpad.muc.redhat.com \
--to=stefanha@gmail.com \
--cc=axboe@kernel.dk \
--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).