From: Stefan Hajnoczi <stefanha@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
qemu block <qemu-block@nongnu.org>, Kevin Wolf <kwolf@redhat.com>,
Fam Zheng <famz@redhat.com>
Subject: Re: [Qemu-devel] Multiqueue block layer
Date: Mon, 19 Feb 2018 18:41:54 +0000 [thread overview]
Message-ID: <CAJSP0QX81kB2PKJU7FG3vY6E9Z2yrysaezrz9wS2v3KHaT2uAg@mail.gmail.com> (raw)
In-Reply-To: <CAJSP0QV5mrt8RiKxXUfXkk7UPLHtwJMUOvcj77Ro43FP=5MkFg@mail.gmail.com>
By the way, one thing that makes me nervous is that we lack an
explicit "request queue" or "per-queue" concept. State can either be
per-BlockDriverState (shared state) or per-request, but not per-queue.
So far there hasn't been a need for per-queue state but there may be
opportunities to eliminate locking if we can replace shared state with
per-queue state.
Stefan
next prev parent reply other threads:[~2018-02-19 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 18:20 [Qemu-devel] Multiqueue block layer Stefan Hajnoczi
2018-02-19 18:03 ` Paolo Bonzini
2018-02-19 18:38 ` Stefan Hajnoczi
2018-02-19 18:41 ` Stefan Hajnoczi [this message]
2018-02-19 18:59 ` Alexandre DERUMIER
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=CAJSP0QX81kB2PKJU7FG3vY6E9Z2yrysaezrz9wS2v3KHaT2uAg@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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).