From: Evgeny Yakovlev <eyakovlev@virtuozzo.com>
To: Eric Blake <eblake@redhat.com>, "Denis V. Lunev" <den@openvz.org>,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/3] block: ignore flush requests when storage is clean
Date: Fri, 24 Jun 2016 18:54:28 +0300 [thread overview]
Message-ID: <576D57B4.30601@virtuozzo.com> (raw)
In-Reply-To: <576D524D.9020400@redhat.com>
On 24.06.2016 18:31, Eric Blake wrote:
> On 06/24/2016 09:06 AM, Denis V. Lunev wrote:
>> From: Evgeny Yakovlev <eyakovlev@virtuozzo.com>
>>
>> Some guests (win2008 server for example) do a lot of unnecessary
>> flushing when underlying media has not changed. This adds additional
>> overhead on host when calling fsync/fdatasync.
>>
>> This change introduces a dirty flag in BlockDriverState which is set
>> in bdrv_set_dirty and is checked in bdrv_co_flush. This allows us to
>> avoid unnesessary flushing when storage is clean.
> s/unnesessary/unnecessary/ (I pointed this out against v2
> https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg05817.html,
> which makes me wonder if anything else was missed)
Yeah, i fixed that but messed up committing a change in commit message.
Will be fixed in rebased version.
>> The problem with excessive flushing was found by a performance test
>> which does parallel directory tree creation (from 2 processes).
>> Results improved from 0.424 loops/sec to 0.432 loops/sec.
>> Each loop creates 10^3 directories with 10 files in each.
>>
>> Signed-off-by: Evgeny Yakovlev <eyakovlev@virtuozzo.com>
>> Signed-off-by: Denis V. Lunev <den@openvz.org>
>> CC: Kevin Wolf <kwolf@redhat.com>
>> CC: Max Reitz <mreitz@redhat.com>
>> CC: Stefan Hajnoczi <stefanha@redhat.com>
>> CC: Fam Zheng <famz@redhat.com>
>> CC: John Snow <jsnow@redhat.com>
>> ---
>> +++ b/include/block/block_int.h
>> @@ -418,6 +418,8 @@ struct BlockDriverState {
>> int sg; /* if true, the device is a /dev/sg* */
>> int copy_on_read; /* if true, copy read backing sectors into image
>> note this is a reference count */
>> +
>> + bool dirty;
>> bool probed;
>>
> Conflicts with the current state of Kevin's block branch (due to my
> reordering and conversion of bool parameters); so you'll want to rebase.
>
Ok
next prev parent reply other threads:[~2016-06-24 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 15:06 [Qemu-devel] [PATCH 0/3] block: ignore flush requests when storage is clean Denis V. Lunev
2016-06-24 15:06 ` [Qemu-devel] [PATCH 1/3] " Denis V. Lunev
2016-06-24 15:31 ` Eric Blake
2016-06-24 15:54 ` Evgeny Yakovlev [this message]
2016-06-28 21:01 ` Paolo Bonzini
2016-06-29 7:36 ` Paolo Bonzini
2016-06-29 8:32 ` Denis V. Lunev
2016-06-24 15:06 ` [Qemu-devel] [PATCH 2/3] ide: ignore retry_unit check for non-retry operations Denis V. Lunev
2016-06-28 20:56 ` Paolo Bonzini
2016-06-29 8:35 ` Evgeny Yakovlev
2016-06-29 10:41 ` Paolo Bonzini
2016-06-24 15:06 ` [Qemu-devel] [PATCH 3/3] tests: in IDE and AHCI tests perform DMA write before flushing Denis V. Lunev
2016-06-24 15:22 ` [Qemu-devel] [PATCH 0/3] block: ignore flush requests when storage is clean Eric Blake
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=576D57B4.30601@virtuozzo.com \
--to=eyakovlev@virtuozzo.com \
--cc=den@openvz.org \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--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).