[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 1.8 4/6] block/iscsi: set bdi->cluster_size
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-devel] [PATCH 1.8 4/6] block/iscsi: set bdi->cluster_size |
Date: |
Mon, 25 Nov 2013 15:51:09 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130923 Thunderbird/17.0.9 |
Il 25/11/2013 14:57, Peter Lieven ha scritto:
> + /* Guess the internal cluster (page) size of the iscsi target by the
> means
> + * of opt_unmap_gran. Transfer the unmap granularity only if it has a
> + * reasonable size for bdi->cluster_size */
> + if (iscsilun->bl.opt_unmap_gran * iscsilun->block_size >= 64 * 1024 &&
> + iscsilun->bl.opt_unmap_gran * iscsilun->block_size <= 16 * 1024 *
> 1024) {
> + bdi->cluster_size = iscsilun->bl.opt_unmap_gran *
> iscsilun->block_size;
> + }
I think you are mixing many different concepts:
* The optimal unmap granularity is good as a suggestion for the cluster
size of higher-level formats.
* The optimal transfer granularity (block limits page, bytes 6-7,
min_io_size in Linux) could be used to adjust the length of transfers in
"qemu-img convert". I have not really thought much about *how* to do it.
* The optimal transfer (block limits page, bytes 12-15, opt_io_size in
Linux) should not be used in "qemu-img convert", I think, unless you can
actually report performance improvements. This is because in "qemu-img
convert" we need to write the data anyway to the target. We cannot
schedule other commands between two transfers. So I don't think any
delays incurred by a very large write should matter.
The maximum transfer length (block limits page, bytes 8-11) should be
handled instead in the iSCSI driver, but I do not see the need to do
this unless we have reports of something not working.
Paolo
- Re: [Qemu-devel] [PATCH 1.8 3/6] qemu-img: add option to specify alternate iobuffer size, (continued)
- Re: [Qemu-devel] [PATCH 1.8 3/6] qemu-img: add option to specify alternate iobuffer size, Peter Lieven, 2013/11/25
- Re: [Qemu-devel] [PATCH 1.8 3/6] qemu-img: add option to specify alternate iobuffer size, Peter Lieven, 2013/11/25
- Re: [Qemu-devel] [PATCH 1.8 3/6] qemu-img: add option to specify alternate iobuffer size, Paolo Bonzini, 2013/11/25
- Re: [Qemu-devel] [PATCH 1.8 3/6] qemu-img: add option to specify alternate iobuffer size, Peter Lieven, 2013/11/25
- Re: [Qemu-devel] [PATCH 1.8 3/6] qemu-img: add option to specify alternate iobuffer size, Paolo Bonzini, 2013/11/25
- Re: [Qemu-devel] [PATCH 1.8 3/6] qemu-img: add option to specify alternate iobuffer size, Peter Lieven, 2013/11/25
[Qemu-devel] [PATCH 1.8 2/6] qemu-img: fix usage instruction for qemu-img convert, Peter Lieven, 2013/11/25
[Qemu-devel] [PATCH 1.8 1/6] qemu-img: add support for skipping zeroes in input during convert, Peter Lieven, 2013/11/25
[Qemu-devel] [PATCH 1.8 4/6] block/iscsi: set bdi->cluster_size, Peter Lieven, 2013/11/25
[Qemu-devel] [PATCH 1.8 6/6] qemu-img: add option to show progress in sectors, Peter Lieven, 2013/11/25
[Qemu-devel] [PATCH 1.8 5/6] qemu-img: add option to align writes to cluster_sectors during convert, Peter Lieven, 2013/11/25
Re: [Qemu-devel] [PATCH 1.8 5/6] qemu-img: add option to align writes to cluster_sectors during convert, Peter Lieven, 2013/11/25
Re: [Qemu-devel] [PATCH 1.8 5/6] qemu-img: add option to align writes to cluster_sectors during convert, Paolo Bonzini, 2013/11/25