From: Paolo Bonzini <pbonzini@redhat.com>
To: James Bottomley <JBottomley@parallels.com>
Cc: "Jason J. Herne"
<public-hernejj-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-usb@vger.kernel.org, Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH] USB enclosures seem to require read(16) with >2TB drives
Date: Mon, 12 Nov 2012 16:35:25 +0100 [thread overview]
Message-ID: <50A1173D.8090603@redhat.com> (raw)
In-Reply-To: <1352733055.2449.34.camel@dabdike.int.hansenpartnership.com>
Il 12/11/2012 16:10, James Bottomley ha scritto:
>> Actually it only turns it on for large capacity drives, as said in the
>> comment. sdp->force_read_16 only matters for >2TB drives:
>
> If you follow the discussion, we'll need to turn it on for some drives
> regardless of size.
Even if the two reasons to use r/w(16) commands were setting the same
flag, it would be handled in a separate patch; it doesn't really make
sense to complicate the code now when a one-liner does it.
The proposed change is not part of the Oct 31st draft available on
t10.org, for what we know the discussion could end up in nothing.
>> > Any reason not to do this always on >2TB drives, which basically means
>> > changing this:
>> >
>> > - } else if (block > 0xffffffff) {
>> > + } else if (sdkp->capacity > 0xffffffff) {
>> >
>> > and nothing else?
> Because of the coming T10 mandate in SBC-4 deprecating everything other
> than the 16 byte commands.
And would this change make the upcoming patch for SBC-4 support longer
or harder to review?
Paolo
next prev parent reply other threads:[~2012-11-12 15:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 16:08 [PATCH] USB enclosures seem to require read(16) with >2TB drives Jason J. Herne
2012-11-09 16:33 ` Elliott, Robert (Server Storage)
[not found] ` <94D0CD8314A33A4D9D801C0FE68B40294C344C61-NSOR0jG+XgMSZAcGdq5asR6epYMZPwEe5NbjCUgZEJk@public.gmane.org>
2012-11-11 11:17 ` Stefan Richter
2012-11-12 8:18 ` Stefan Richter
2012-11-12 11:17 ` James Bottomley
2012-11-12 11:33 ` James Bottomley
[not found] ` <1352719990.2449.23.camel-sFMDBYUN5F8GjUHQrlYNx2Wm91YjaHnnhRte9Li2A+AAvxtiuMwx3w@public.gmane.org>
2012-11-12 14:31 ` Paolo Bonzini
[not found] ` <50A10856.6090009-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-11-12 15:01 ` Jason J. Herne
2012-11-12 15:28 ` James Bottomley
2012-11-12 15:10 ` James Bottomley
2012-11-12 15:22 ` Jason J. Herne
2012-11-12 15:35 ` Paolo Bonzini [this message]
[not found] ` <50A1173D.8090603-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-11-12 16:06 ` Alan Stern
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=50A1173D.8090603@redhat.com \
--to=pbonzini@redhat.com \
--cc=JBottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=public-hernejj-Re5JQEeQqe8AvxtiuMwx3w@plane.gmane.org \
--cc=stern@rowland.harvard.edu \
/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).