From: Christoph Hellwig <hch@lst.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "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: Tue, 30 Dec 2014 12:28:09 +0100 [thread overview]
Message-ID: <20141230112809.GA1360@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1412282200040.24524-100000@netrider.rowland.org>
On Sun, Dec 28, 2014 at 10:10:01PM -0500, Alan Stern wrote:
> (Is this a USB device? Presumably you wouldn't have CC'ed the
> linux-usb and usb-storage mailing lists if it wasn't...)
It's a usb attached device. From the inquity information and the
product name it looks like a SATA device attached via a usb bridge.
> The only limits usb-storage imposes on max_sectors are those needed to
> work around bugs in the devices' USB bridges. (Okay, there's also
> something for tape drive devices, but it probably doesn't belong in
> usb-storage -- it should be handled by the SCSI tape driver.)
>
> If the ATA layer needs to set a limit on max_sectors, why doesn't it
> simply go ahead and do so?
Because the ATA layer doesn't control the device, the bridge does.
And it seems like it doesn't communicate the maximum transfer size
properly.
next prev parent reply other threads:[~2014-12-30 11:28 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 [this message]
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
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=20141230112809.GA1360@lst.de \
--to=hch@lst.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.