From: Peter Lieven <pl@kamp.de>
To: Max Reitz <mreitz@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, ronniesahlberg@gmail.com,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCHv4 3/4] block/iscsi: set max_transfer_length
Date: Sat, 25 Oct 2014 17:16:05 +0200 [thread overview]
Message-ID: <544BBEB5.4040004@kamp.de> (raw)
In-Reply-To: <5448E403.30602@redhat.com>
Am 23.10.2014 um 13:18 schrieb Max Reitz:
> On 2014-10-16 at 09:54, Peter Lieven wrote:
>> the limit of 0xffffff for 16 byte CDBs is intentional to
>> avoid overflows on 32-bit architectures.
>
> How is it related to 32 bit? I somehow feel like it has to do something with the result of sector_lun2qemu() which involves block_size...
iscsilun->bl.max_xfer_len is 32-bit unsigned while nb_sectors is usually signed. Furthermore as you suspected nb_sectors is always 512Byte sectors
while iscsilun->block_size can be 4k or even more.
I will change the code to set max_xfer_len to 0xffffffff and limit the output of sector_lun2qemu() to INT_MAX in the bs->bl.max_transfer_length case.
However, in real life you will never want to have a transfer of 0x3fffffff blocks, won't you?
Peter
>
>> Signed-off-by: Peter Lieven <pl@kamp.de>
>> Reviewed-by: Ronnie Sahlberg <ronniesahlberg@gmail.com>
>> ---
>> block/iscsi.c | 12 ++++++++++--
>> 1 file changed, 10 insertions(+), 2 deletions(-)
>>
>> diff --git a/block/iscsi.c b/block/iscsi.c
>> index 3a01de0..c873d13 100644
>> --- a/block/iscsi.c
>> +++ b/block/iscsi.c
>> @@ -1449,10 +1449,18 @@ static void iscsi_close(BlockDriverState *bs)
>> static void iscsi_refresh_limits(BlockDriverState *bs, Error **errp)
>> {
>> - IscsiLun *iscsilun = bs->opaque;
>> -
>> /* We don't actually refresh here, but just return data queried in
>> * iscsi_open(): iscsi targets don't change their limits. */
>> +
>> + IscsiLun *iscsilun = bs->opaque;
>> + uint32_t max_xfer_len = iscsilun->use_16_for_rw ? 0xffffff : 0xffff;
>> +
>> + if (iscsilun->bl.max_xfer_len) {
>> + max_xfer_len = MIN(max_xfer_len, iscsilun->bl.max_xfer_len);
>> + }
>> +
>> + bs->bl.max_transfer_length = sector_lun2qemu(max_xfer_len, iscsilun);
>> +
>> if (iscsilun->lbp.lbpu) {
>> if (iscsilun->bl.max_unmap < 0xffffffff) {
>> bs->bl.max_discard = sector_lun2qemu(iscsilun->bl.max_unmap,
>
next prev parent reply other threads:[~2014-10-25 15:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 7:54 [Qemu-devel] [PATCHv4 0/4] introduce max_transfer_length Peter Lieven
2014-10-16 7:54 ` [Qemu-devel] [PATCHv4 1/4] util: introduce MIN_NON_ZERO Peter Lieven
2014-10-22 22:34 ` Eric Blake
2014-10-23 10:10 ` Max Reitz
2014-10-16 7:54 ` [Qemu-devel] [PATCHv4 2/4] BlockLimits: introduce max_transfer_length Peter Lieven
2014-10-23 11:10 ` Max Reitz
2014-10-16 7:54 ` [Qemu-devel] [PATCHv4 3/4] block/iscsi: set max_transfer_length Peter Lieven
2014-10-23 11:18 ` Max Reitz
2014-10-25 15:16 ` Peter Lieven [this message]
2014-10-27 8:16 ` Max Reitz
2014-10-16 7:54 ` [Qemu-devel] [PATCHv4 4/4] block: avoid creating oversized writes in multiwrite_merge Peter Lieven
2014-10-23 11:23 ` Max Reitz
2014-10-25 15:19 ` Peter Lieven
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=544BBEB5.4040004@kamp.de \
--to=pl@kamp.de \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--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).