From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Lieven <pl@kamp.de>
Cc: kwolf@redhat.com, stefanha@redhat.com, qemu-devel@nongnu.org,
ronniesahlberg@gmail.com
Subject: Re: [Qemu-devel] [PATCHv6 17/17] block/raw: copy BlockLimits on raw_open
Date: Thu, 24 Oct 2013 11:06:25 +0100 [thread overview]
Message-ID: <5268F121.80200@redhat.com> (raw)
In-Reply-To: <5268E47B.4060107@kamp.de>
Il 24/10/2013 10:12, Peter Lieven ha scritto:
>> This must be moved before the introduction of BlockLimits in the iscsi
>> driver, or patches that use BlockLimits in block.c will not have any
>> effect.
> You are the first to mention this. I was thinking the whole series will
> be seen as once so it shouldn't matter.
In general, series should keep old functionality at all stages. This
helps when someone reports a regression, because we can ask them to
bisect and not have them burdened by problems in the middle of a series.
(It would also help you debugging things, if this series turned out to
have a bug).
After patch 10 of this series, an iSCSI array will stop receiving split
requests for large discards. This may introduce spurious failures.
I made the same remark on patch 11, but that patch alone is not enough
to restore this; you need this one too for patch 11 to have any effect.
So the correct order is patch 17 first, then patch 11, then patch 10.
In other word, remove code only after it has become dead.
Paolo
prev parent reply other threads:[~2013-10-24 10:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 7:46 [Qemu-devel] [PATCHv6 00/17] block: logical block provisioning enhancements Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 01/17] block: make BdrvRequestFlags public Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 02/17] block: add flags to bdrv_*_write_zeroes Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 03/17] block: introduce BDRV_REQ_MAY_UNMAP request flag Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 04/17] block: add logical block provisioning info to BlockDriverInfo Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 05/17] block: add wrappers for logical block provisioning information Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 06/17] block/iscsi: add .bdrv_get_info Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 07/17] block: add BlockLimits structure to BlockDriverState Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 08/17] block: honour BlockLimits in bdrv_co_do_write_zeroes Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 09/17] block: honour BlockLimits in bdrv_co_discard Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 10/17] iscsi: simplify iscsi_co_discard Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 11/17] iscsi: set limits in BlockDriverState Peter Lieven
2013-10-24 9:07 ` Paolo Bonzini
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 12/17] iscsi: add bdrv_co_write_zeroes Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 13/17] block: introduce bdrv_make_zero Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 14/17] block/get_block_status: fix BDRV_BLOCK_ZERO for unallocated blocks Peter Lieven
2013-10-24 9:09 ` Paolo Bonzini
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 15/17] qemu-img: add support for fully allocated images Peter Lieven
2013-10-24 9:12 ` Paolo Bonzini
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 16/17] qemu-img: conditionally zero out target on convert Peter Lieven
2013-10-24 9:13 ` Paolo Bonzini
2013-10-24 9:17 ` Peter Lieven
2013-10-24 7:46 ` [Qemu-devel] [PATCHv6 17/17] block/raw: copy BlockLimits on raw_open Peter Lieven
2013-10-24 9:10 ` Paolo Bonzini
2013-10-24 9:12 ` Peter Lieven
2013-10-24 10:06 ` Paolo Bonzini [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=5268F121.80200@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--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).