From: Kevin Wolf <kwolf@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: famz@redhat.com, benoit@irqsave.net, ming.lei@canonical.com,
armbru@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
pbonzini@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 0/5] this series adds the long missing multiread support to virtio-blk.
Date: Mon, 2 Feb 2015 17:09:29 +0100 [thread overview]
Message-ID: <20150202160929.GJ9478@noname.redhat.com> (raw)
In-Reply-To: <1422885142-6391-1-git-send-email-pl@kamp.de>
Am 02.02.2015 um 14:52 hat Peter Lieven geschrieben:
> some remarks:
> - i introduced rd_merged and wr_merged block accounting stats to
> blockstats as a generic interface which can be set from any
> driver that will introduce multirequest merging in the future.
> - the old multiwrite interface is still there and might be removed.
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2015-02-02 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 13:52 [Qemu-devel] [PATCH v4 0/5] this series adds the long missing multiread support to virtio-blk Peter Lieven
2015-02-02 13:52 ` [Qemu-devel] [PATCH v4 1/5] block: add accounting for merged requests Peter Lieven
2015-02-02 13:52 ` [Qemu-devel] [PATCH v4 2/5] hw/virtio-blk: add a constant for max number of " Peter Lieven
2015-02-02 13:52 ` [Qemu-devel] [PATCH v4 3/5] block-backend: expose bs->bl.max_transfer_length Peter Lieven
2015-02-02 13:52 ` [Qemu-devel] [PATCH v4 4/5] virtio-blk: introduce multiread Peter Lieven
2015-02-02 13:52 ` [Qemu-devel] [PATCH v4 5/5] virtio-blk: add a knob to disable request merging Peter Lieven
2015-02-02 16:09 ` Kevin Wolf [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=20150202160929.GJ9478@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=benoit@irqsave.net \
--cc=famz@redhat.com \
--cc=ming.lei@canonical.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--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).