public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jeff@garzik.org>
Cc: Sergei Shtylyov <sshtylyov@ru.mvista.com>,
	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 16:28:33 +0100	[thread overview]
Message-ID: <1157988513.23085.159.camel@localhost.localdomain> (raw)
In-Reply-To: <45057651.8000404@garzik.org>

Ar Llu, 2006-09-11 am 10:44 -0400, ysgrifennodd Jeff Garzik:
> > 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.
> 
> Where in drivers/ide is it limited to 255?

Being a sensible sanity check it was removed, and that was a small
mistake. Some 2.4 also has a 256 limit and it broken various transparent
raid units, older Maxtors(1Gb or so), some IBM drives etc. Got fixed in
-ac but never in base.

The failure pattern is pretty ugly too, your box runs and runs and
eventually you get a linear 256 sector I/O and it all blows up,
sometimes. The IBM's abort the xfer but the maxtors may or may not get
it right (its as if half the firmware has the right test).

We could perhaps do it by ATA version - 255 for ATA < 3 256 for ATA 3+,
lots for LBA48 ? Thats assuming you can show 256 sectors is faster than
255. I'd bet for normal I/O its unmeasurably small.

Alan


  parent reply	other threads:[~2006-09-11 15:05 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 [this message]
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
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=1157988513.23085.159.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --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