From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: "mreitz@redhat.com" <mreitz@redhat.com>,
"kwolf@redhat.com" <kwolf@redhat.com>,
"fam@euphon.net" <fam@euphon.net>,
"stefanha@redhat.com" <stefanha@redhat.com>,
"eblake@redhat.com" <eblake@redhat.com>,
Denis Lunev <den@virtuozzo.com>
Subject: Re: [Qemu-devel] [PATCH v2 for 4.1 0/2] avoid lseek on block_status
Date: Mon, 22 Apr 2019 09:58:38 +0000 [thread overview]
Message-ID: <2bd2faa2-adeb-924f-656b-bdce6cd5d164@virtuozzo.com> (raw)
In-Reply-To: <20190408162617.258535-1-vsementsov@virtuozzo.com>
ping
08.04.2019 19:26, Vladimir Sementsov-Ogievskiy wrote:
> Hi!
>
> It's a continuation for
> "[PATCH] qcow2: avoid lseek on block_status if possible"
> https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg06598.html
>
> performance results for block-status on tmpfs [tests originally by Kevin,
> now they are in 01]:
>
> ./tests/perf/block/qcow2/convert-blockstatus /ramdisk/x
>
> after 01:
>
> plain: 81.77
> forward: 82.61
> prealloc: 0.01
>
> after 02:
>
> plain: 0.12
> forward: 0.12
> prealloc: 0.01
>
> v2:
> 01: new
> 02: [mostly by Kevin's comments]
> - rewritten to go through new flag BDRV_BLOCK_RECURSE
> - never retry detection if failed for first time
> - rewrite detection to do less iterations and to be more simple
>
> iotests 102 behavior changed [and not sure about other two ones
> in comparison with v1, but it seems it doesn't matter]
>
> also, patch subject changed, as now it's a generic change for
> block layer
>
>
> Vladimir Sementsov-Ogievskiy (2):
> tests/perf: Test lseek influence on qcow2 block-status
> block: avoid recursive block_status call if possible
>
> block/qcow2.h | 4 ++
> include/block/block.h | 8 ++-
> block/io.c | 9 ++-
> block/qcow2-refcount.c | 32 ++++++++++
> block/qcow2.c | 11 ++++
> tests/perf/block/qcow2/convert-blockstatus | 71 ++++++++++++++++++++++
> tests/qemu-iotests/102 | 2 +-
> tests/qemu-iotests/102.out | 3 +-
> tests/qemu-iotests/141.out | 2 +-
> tests/qemu-iotests/144.out | 2 +-
> 10 files changed, 138 insertions(+), 6 deletions(-)
> create mode 100755 tests/perf/block/qcow2/convert-blockstatus
>
--
Best regards,
Vladimir
WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"fam@euphon.net" <fam@euphon.net>,
Denis Lunev <den@virtuozzo.com>,
"mreitz@redhat.com" <mreitz@redhat.com>,
"stefanha@redhat.com" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 for 4.1 0/2] avoid lseek on block_status
Date: Mon, 22 Apr 2019 09:58:38 +0000 [thread overview]
Message-ID: <2bd2faa2-adeb-924f-656b-bdce6cd5d164@virtuozzo.com> (raw)
Message-ID: <20190422095838.0d8JP6OmaQ_2Ka1gmjqfTxqBaTJDj9-WR_CU8p8EZPU@z> (raw)
In-Reply-To: <20190408162617.258535-1-vsementsov@virtuozzo.com>
ping
08.04.2019 19:26, Vladimir Sementsov-Ogievskiy wrote:
> Hi!
>
> It's a continuation for
> "[PATCH] qcow2: avoid lseek on block_status if possible"
> https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg06598.html
>
> performance results for block-status on tmpfs [tests originally by Kevin,
> now they are in 01]:
>
> ./tests/perf/block/qcow2/convert-blockstatus /ramdisk/x
>
> after 01:
>
> plain: 81.77
> forward: 82.61
> prealloc: 0.01
>
> after 02:
>
> plain: 0.12
> forward: 0.12
> prealloc: 0.01
>
> v2:
> 01: new
> 02: [mostly by Kevin's comments]
> - rewritten to go through new flag BDRV_BLOCK_RECURSE
> - never retry detection if failed for first time
> - rewrite detection to do less iterations and to be more simple
>
> iotests 102 behavior changed [and not sure about other two ones
> in comparison with v1, but it seems it doesn't matter]
>
> also, patch subject changed, as now it's a generic change for
> block layer
>
>
> Vladimir Sementsov-Ogievskiy (2):
> tests/perf: Test lseek influence on qcow2 block-status
> block: avoid recursive block_status call if possible
>
> block/qcow2.h | 4 ++
> include/block/block.h | 8 ++-
> block/io.c | 9 ++-
> block/qcow2-refcount.c | 32 ++++++++++
> block/qcow2.c | 11 ++++
> tests/perf/block/qcow2/convert-blockstatus | 71 ++++++++++++++++++++++
> tests/qemu-iotests/102 | 2 +-
> tests/qemu-iotests/102.out | 3 +-
> tests/qemu-iotests/141.out | 2 +-
> tests/qemu-iotests/144.out | 2 +-
> 10 files changed, 138 insertions(+), 6 deletions(-)
> create mode 100755 tests/perf/block/qcow2/convert-blockstatus
>
--
Best regards,
Vladimir
next prev parent reply other threads:[~2019-04-22 9:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 16:26 [Qemu-devel] [PATCH v2 for 4.1 0/2] avoid lseek on block_status Vladimir Sementsov-Ogievskiy
2019-04-08 16:26 ` Vladimir Sementsov-Ogievskiy
2019-04-08 16:26 ` [Qemu-devel] [PATCH v2 1/2] tests/perf: Test lseek influence on qcow2 block-status Vladimir Sementsov-Ogievskiy
2019-04-08 16:26 ` Vladimir Sementsov-Ogievskiy
2019-04-08 16:26 ` [Qemu-devel] [PATCH v2 2/2] block: avoid recursive block_status call if possible Vladimir Sementsov-Ogievskiy
2019-04-08 16:26 ` Vladimir Sementsov-Ogievskiy
2019-05-22 10:32 ` Kevin Wolf
2019-05-27 15:13 ` Max Reitz
2019-05-28 6:39 ` Vladimir Sementsov-Ogievskiy
2019-05-28 15:47 ` Max Reitz
2019-04-22 9:58 ` Vladimir Sementsov-Ogievskiy [this message]
2019-04-22 9:58 ` [Qemu-devel] [PATCH v2 for 4.1 0/2] avoid lseek on block_status Vladimir Sementsov-Ogievskiy
2019-05-06 15:14 ` Vladimir Sementsov-Ogievskiy
2019-05-21 7:50 ` [Qemu-devel] ping " Vladimir Sementsov-Ogievskiy
2019-05-22 10:47 ` [Qemu-devel] " Kevin Wolf
2019-05-22 11:30 ` Vladimir Sementsov-Ogievskiy
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=2bd2faa2-adeb-924f-656b-bdce6cd5d164@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@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).