From: Jens Axboe <axboe@kernel.dk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: What's in libata-dev.git
Date: Mon, 11 Sep 2006 17:06:15 +0200 [thread overview]
Message-ID: <20060911150615.GB4955@suse.de> (raw)
In-Reply-To: <1157986974.23085.147.camel@localhost.localdomain>
On Mon, Sep 11 2006, Alan Cox wrote:
> Ar Llu, 2006-09-11 am 17:47 +0400, ysgrifennodd Sergei Shtylyov:
> > It's not likely I'll be able to try it. But I'm absolutely sure that drive
> > aborted the read commands with the sector count of 0 (i.e. 256 actually). The
> > exact model was IBM DHEA-34331.
>
> Several people reported this problem when we tried 256 years ago in
> drivers/ide. You might want to do 256 for SATA Jeff but please don't do
> 256 for PATA. Reading specs is too hard for some people ;)
>
> Some drives abort the xfer, some just choked.
Ehm it's 256 now and it has been for a looong time. The few cases I've
seen where people claimed it broke, turned out to be something else.
I've still haven't seen a valid report on this.
It might sound obscure that 0 means 256 sectors, but it's really not a
hidden obscure fact - people do know. I'm all for being conservative
where it matters, but I'm siding with Jeff on this one. I suspect that
Windows uses 256 as well, which basically means that we're in the clear.
--
Jens Axboe
next prev parent reply other threads:[~2006-09-11 15:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 13:22 What's in libata-dev.git Jeff Garzik
2006-09-11 13:35 ` Sergei Shtylyov
2006-09-11 13:37 ` Jeff Garzik
2006-09-11 13:47 ` Sergei Shtylyov
2006-09-11 13:49 ` Jeff Garzik
2006-09-11 14:53 ` Linus Torvalds
2006-09-11 15:24 ` Jeff Garzik
2006-09-12 8:42 ` Helge Hafting
2006-09-13 1:50 ` Tejun Heo
2006-09-11 15:02 ` Alan Cox
2006-09-11 14:44 ` Jeff Garzik
2006-09-11 15:05 ` Sergei Shtylyov
2006-09-11 15:28 ` Alan Cox
2006-09-11 15:21 ` Sergei Shtylyov
2006-09-11 15:37 ` Jens Axboe
2006-09-11 15:50 ` Jeff Garzik
2006-09-11 20:01 ` Jens Axboe
2006-09-11 20:14 ` Jeff Garzik
2006-09-11 20:23 ` Jens Axboe
2006-09-11 16:04 ` Linus Torvalds
2006-09-11 19:51 ` Jens Axboe
2006-09-11 23:00 ` Alan Cox
2006-09-11 22:53 ` Greg Freemyer
2006-09-12 5:22 ` Jens Axboe
2006-09-11 16:26 ` Alan Cox
2006-09-11 19:51 ` Jens Axboe
2006-09-11 15:06 ` Jens Axboe [this message]
2006-10-04 17:57 ` Mark Lord
2006-10-04 18:03 ` Sergei Shtylyov
2006-10-04 18:48 ` Mark Lord
-- strict thread matches above, loose matches on Subject: below --
2007-01-24 7:26 Jeff Garzik
2007-01-24 17:26 ` Mark Lord
2007-01-24 19:19 ` Jeff Garzik
2006-05-24 7:08 Jeff Garzik
2006-04-18 9:54 Jeff Garzik
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=20060911150615.GB4955@suse.de \
--to=axboe@kernel.dk \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
--cc=torvalds@osdl.org \
/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