From: Christoph Hellwig <hch@lst.de>
To: Douglas Gilbert <dgilbert@interlog.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Christoph Hellwig <hch@lst.de>,
"Kenneth R. Crudup" <kenny@panix.com>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
linux-usb@vger.kernel.org, usb-storage@lists.one-eyed-alien.net
Subject: Re: Issues with commit 34b48db6 ("block: remove artifical max_hw_sectors cap")
Date: Mon, 5 Jan 2015 18:18:38 +0100 [thread overview]
Message-ID: <20150105171838.GB30028@lst.de> (raw)
In-Reply-To: <54A2D07B.4040607@interlog.com>
On Tue, Dec 30, 2014 at 11:19:07AM -0500, Douglas Gilbert wrote:
> In SCSI, the VPD page 0xb0 (Block limits) has a "Maximum transfer
> length" field (32 bits long). Its units are logical blocks. Useful
> if >0 as 0 means "unreported".
>
> USB to SATA bridges should comply with SAT. However SAT and SAT-2
> don't even mention that VPD page. SAT-3 and SAT-4 mention that page
> but have "unspecified" next to that field. Basically useless.
Maybe we need to cap the max sectors value to something fairly low
unless we have the block limits VPD page and it contains useful information.
prev parent reply other threads:[~2015-01-05 17:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.10.1412211420560.4323@tosh-p75a>
2014-12-23 8:31 ` Issues with commit 34b48db6 ("block: remove artifical max_hw_sectors cap") Christoph Hellwig
2014-12-24 7:48 ` Kenneth R. Crudup
2014-12-24 8:18 ` Kenneth R. Crudup
2014-12-27 15:13 ` Christoph Hellwig
2014-12-29 3:10 ` Alan Stern
2014-12-30 11:28 ` Christoph Hellwig
2014-12-30 15:34 ` Alan Stern
2014-12-30 15:50 ` James Bottomley
2014-12-30 16:12 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.1412301109050.32416-100000-pYrvlCTfrz9XsRXLowluHWD2FQJk+8+b@public.gmane.org>
2014-12-30 16:25 ` James Bottomley
2014-12-30 16:45 ` Alan Stern
2014-12-30 16:54 ` James Bottomley
2014-12-30 16:19 ` Douglas Gilbert
2014-12-30 16:36 ` Kenneth R. Crudup
2015-01-05 17:19 ` Christoph Hellwig
2015-01-05 20:07 ` Alan Stern
2015-01-05 20:19 ` Kenneth R. Crudup
2015-01-19 9:45 ` Kenneth R. Crudup
2015-01-19 15:55 ` Alan Stern
2015-01-19 22:59 ` Kenneth R. Crudup
2015-02-08 22:11 ` Kenneth R. Crudup
2015-01-05 17:18 ` Christoph Hellwig [this message]
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=20150105171838.GB30028@lst.de \
--to=hch@lst.de \
--cc=dgilbert@interlog.com \
--cc=kenny@panix.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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