From: Fam Zheng <famz@redhat.com>
To: arei.gonglei@huawei.com
Cc: pbonzini@redhat.com, stefanha@redhat.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] virtio-blk: trivial code optimization
Date: Mon, 9 Nov 2015 14:48:52 +0800 [thread overview]
Message-ID: <20151109064852.GA18363@ad.usersys.redhat.com> (raw)
In-Reply-To: <1447039178-17208-1-git-send-email-arei.gonglei@huawei.com>
On Mon, 11/09 11:19, arei.gonglei@huawei.com wrote:
> From: Gonglei <arei.gonglei@huawei.com>
>
> 1. avoid possible superflous checking
> 2. make code more robustness
>
> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
> ---
> v2: address Paolo's comments, thanks.
> ---
> hw/block/virtio-blk.c | 27 +++++++++------------------
> 1 file changed, 9 insertions(+), 18 deletions(-)
>
> diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
> index 093e475..21f8d72 100644
> --- a/hw/block/virtio-blk.c
> +++ b/hw/block/virtio-blk.c
> @@ -404,24 +404,15 @@ void virtio_blk_submit_multireq(BlockBackend *blk, MultiReqBuffer *mrb)
> for (i = 0; i < mrb->num_reqs; i++) {
> VirtIOBlockReq *req = mrb->reqs[i];
> if (num_reqs > 0) {
> - bool merge = true;
> -
> - /* merge would exceed maximum number of IOVs */
> - if (niov + req->qiov.niov > IOV_MAX) {
> - merge = false;
> - }
> -
> - /* merge would exceed maximum transfer length of backend device */
> - if (req->qiov.size / BDRV_SECTOR_SIZE + nb_sectors > max_xfer_len) {
> - merge = false;
> - }
> -
> - /* requests are not sequential */
> - if (sector_num + nb_sectors != req->sector_num) {
> - merge = false;
> - }
> -
> - if (!merge) {
> + /*
> + * NOTE: We cannot merge the requests in below situations:
> + * 1. requests are not sequential
> + * 2. merge would exceed maximum number of IOVs
> + * 3. merge would exceed maximum transfer length of backend device
> + */
> + if (sector_num + nb_sectors != req->sector_num ||
> + niov > IOV_MAX - req->qiov.niov ||
> + req->qiov.size / BDRV_SECTOR_SIZE + nb_sectors > max_xfer_len) {
> submit_requests(blk, mrb, start, num_reqs, niov);
> num_reqs = 0;
> }
> --
> 1.7.12.4
>
>
>
Reviewed-by: Fam Zheng <famz@redhat.com>
next prev parent reply other threads:[~2015-11-09 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 3:19 [Qemu-devel] [PATCH v2] virtio-blk: trivial code optimization arei.gonglei
2015-11-09 6:48 ` Fam Zheng [this message]
2015-11-09 8:41 ` Paolo Bonzini
2015-11-09 8:51 ` Gonglei
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=20151109064852.GA18363@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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).