From: Peter Lieven <pl@kamp.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
Michael Tokarev <mjt@tls.msk.ru>,
ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block/iscsi: use 16 byte CDBs only when necessary
Date: Tue, 17 Jun 2014 15:45:43 +0200 [thread overview]
Message-ID: <53A04687.3020108@kamp.de> (raw)
In-Reply-To: <53A02AA6.2060006@redhat.com>
On 17.06.2014 13:46, Paolo Bonzini wrote:
> Il 17/06/2014 13:37, Peter Lieven ha scritto:
>> On 17.06.2014 13:15, Paolo Bonzini wrote:
>>> Il 17/06/2014 08:14, Peter Lieven ha scritto:
>>>>>
>>>>
>>>> BTW, while debugging a case with a bigger storage supplier I found
>>>> that open-iscsi seems to do exactly this undeterministic behaviour.
>>>> I have a 3TB LUN. If I access < 2TB sectors it uses READ10/WRITE10 and
>>>> if I go beyond 2TB it changes to READ16/WRITE16.
>>>
>>> Isn't that exactly what your latest patch does for >64K sector writes? :)
>>
>> Not exactly, we choose the default by checking the LUN size. 10 Byte for
>> < 2TB and 16 Byte otherwise.
>
> Yeah, I meant introducing the non-determinism.
>
>> My latest patch makes an exception if a request is bigger than 64K
>> sectors and
>> switches to 16 Byte requests. These would otherwise end in an I/O error.
>
> It could also be split at the block layer, like we do for unmap. I think there's also a maximum transfer size somewhere in the VPD, we could to READ16/WRITE16 if it is >64K sectors.
There is a max_xfer_len in the block limits VPD. But at least in my case its 0 (=no limit). So for <2TB LUNs without
this patch the limit is 64K.
Peter
>
> Paolo
--
Mit freundlichen Grüßen
Peter Lieven
...........................................................
KAMP Netzwerkdienste GmbH
Vestische Str. 89-91 | 46117 Oberhausen
Tel: +49 (0) 208.89 402-50 | Fax: +49 (0) 208.89 402-40
pl@kamp.de | http://www.kamp.de
Geschäftsführer: Heiner Lante | Michael Lante
Amtsgericht Duisburg | HRB Nr. 12154
USt-Id-Nr.: DE 120607556
...........................................................
next prev parent reply other threads:[~2014-06-17 13:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 13:47 [Qemu-devel] [PATCH] block/iscsi: use 16 byte CDBs only when necessary Peter Lieven
2014-06-04 14:00 ` ronnie sahlberg
2014-06-04 14:43 ` Peter Lieven
2014-06-04 14:54 ` ronnie sahlberg
2014-06-05 9:12 ` Michael Tokarev
2014-06-05 9:27 ` Peter Lieven
2014-06-17 6:14 ` Peter Lieven
2014-06-17 11:15 ` Paolo Bonzini
2014-06-17 11:37 ` Peter Lieven
2014-06-17 11:46 ` Paolo Bonzini
2014-06-17 11:50 ` Peter Lieven
2014-06-17 13:45 ` Peter Lieven [this message]
2014-09-01 15:21 ` Peter Lieven
2014-09-02 15:28 ` ronnie sahlberg
2014-09-02 18:14 ` Peter Lieven
2014-09-02 19:30 ` Peter Lieven
2014-09-03 8:09 ` Peter Lieven
2014-09-03 12:31 ` Stefan Hajnoczi
2014-09-03 13:13 ` Peter Lieven
2014-09-03 14:17 ` ronnie sahlberg
2014-09-03 14:18 ` Paolo Bonzini
2014-09-03 14:48 ` ronnie sahlberg
2014-09-03 19:29 ` Peter Lieven
2014-06-04 15:31 ` Paolo Bonzini
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=53A04687.3020108@kamp.de \
--to=pl@kamp.de \
--cc=kwolf@redhat.com \
--cc=mjt@tls.msk.ru \
--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).