From: Peter Lieven <pl@kamp.de>
To: Michael Tokarev <mjt@tls.msk.ru>,
ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@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 08:14:05 +0200 [thread overview]
Message-ID: <539FDCAD.5060006@kamp.de> (raw)
In-Reply-To: <53903469.8070902@msgid.tls.msk.ru>
On 05.06.2014 11:12, Michael Tokarev wrote:
> 04.06.2014 18:00, ronnie sahlberg wrote:
>> That would mean you get to use the 10 version of the cdb even for very
>> large devices (as long as the IO is for blocks at the beginning of the
>> device) and thus provide partial avoidance of this issue for those
>> large devices.
> That may make some bugs "ghosty", so to say. Ie, if there's a bug in/with
> 16 version of a command, you'll hit it only when you actually try to access
> a "far" area of a drive. Which means you're unlikely to hit it while trying
> to reproduce in a clean environment, even after using a large device. Or,
> the bug will be triggered at random, since data placement on the filesystem
> is effectively (from user PoV) random.
>
> To my taste it is better to make it a bit more deterministic.
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.
Peter
next prev parent reply other threads:[~2014-06-17 6:14 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 [this message]
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
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=539FDCAD.5060006@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).