From: Peter Lieven <pl@kamp.de>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, armbru@redhat.com,
stefanha@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCHv2 3/6] block: add a knob to disable multiwrite_merge
Date: Wed, 22 Oct 2014 22:24:13 +0200 [thread overview]
Message-ID: <5448126D.8030106@kamp.de> (raw)
In-Reply-To: <5447F798.1060609@redhat.com>
Am 22.10.2014 um 20:29 schrieb Eric Blake:
> On 10/22/2014 07:21 AM, Peter Lieven wrote:
>> The block layer silently merges write requests since
>> commit 40b4f539. This patch adds a knob to disable
>> this feature as there has been some discussion lately
>> if multiwrite is a good idea at all and as it falsifies
>> benchmarks.
>>
>> Signed-off-by: Peter Lieven <pl@kamp.de>
>> Reviewed-by: Max Reitz <mreitz@redhat.com>
>>
>> Signed-off-by: Peter Lieven <pl@kamp.de>
> Is the double s-o-b intentional?
Mistake
>
>
>> +++ b/hmp.c
>> @@ -348,6 +348,10 @@ void hmp_info_block(Monitor *mon, const QDict *qdict)
>> BlockdevDetectZeroesOptions_lookup[info->value->inserted->detect_zeroes]);
>> }
>>
>> + if (!info->value->inserted->write_merging) {
>> + monitor_printf(mon, " Write Merging: off\n");
>> + }
> Is it also worth printing something if write merging is enabled?
>
Enabled Write Merging is the default since 2009. We do not display
all other defaults as well. But I don't mind.
Peter
next prev parent reply other threads:[~2014-10-22 20:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 13:21 [Qemu-devel] [PATCHv2 0/6] multiwrite patches for 2.2 Peter Lieven
2014-10-22 13:21 ` [Qemu-devel] [PATCHv2 1/6] block: add accounting for merged requests Peter Lieven
2014-10-22 18:20 ` Eric Blake
2014-10-22 20:22 ` Peter Lieven
2014-10-22 13:21 ` [Qemu-devel] [PATCHv2 2/6] block: introduce bdrv_runtime_opts Peter Lieven
2014-10-22 13:21 ` [Qemu-devel] [PATCHv2 3/6] block: add a knob to disable multiwrite_merge Peter Lieven
2014-10-22 18:29 ` Eric Blake
2014-10-22 20:24 ` Peter Lieven [this message]
2014-10-22 13:21 ` [Qemu-devel] [PATCHv2 4/6] hw/virtio-blk: add a constant for max number of merged requests Peter Lieven
2014-10-22 13:21 ` [Qemu-devel] [PATCHv2 5/6] block: add qemu-iotest for write-merge parameter Peter Lieven
2014-10-23 9:59 ` Max Reitz
2014-10-22 13:22 ` [Qemu-devel] [PATCHv2 6/6] block: fix qemu-iotest reference output for test 067 Peter Lieven
2014-10-23 10:03 ` Max Reitz
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=5448126D.8030106@kamp.de \
--to=pl@kamp.de \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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).