linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Helge Hafting <helge.hafting@aitel.hist.no>
Cc: Linus Torvalds <torvalds@osdl.org>, Jeff Garzik <jeff@garzik.org>,
	Sergei Shtylyov <sshtylyov@ru.mvista.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@osdl.org>
Subject: Re: What's in libata-dev.git
Date: Wed, 13 Sep 2006 10:50:28 +0900	[thread overview]
Message-ID: <450763E4.6010602@gmail.com> (raw)
In-Reply-To: <45067312.7020900@aitel.hist.no>

Helge Hafting wrote:
> How about a simple and harmless test?
> When an IDE disk is accessed for the first time, perhaps when
> the partition table is read - issue a 256-sector read and see
> what happens.  If it works - fine.  If not, tag the thing as
> supporting max 255 sectors.
> 
> No wrecking of file systems, and full performance for
> the vast majority.

Before implementing anything like that, we need a test case.  We don't 
know how a faulty drive reacts on such cases.  If it actively aborts the 
command, we can reduce the limit to 255 sectors after upper layer issues 
such command, no need to do it earlier.  If it times out, we can't do it 
during boot and it will suck later too.  If it silently corrupts data 
(highly unlikely), we need to detect the condition during boot.

I don't think it matters all that much anyway.  IDE has been running w/ 
256 sectors for a loooong time and someone who seeks performance from 
LBA28 only drive has bigger problems (also I don't think 255 would be 
noticeably slower than 256).

-- 
tejun

  reply	other threads:[~2006-09-13  1:50 UTC|newest]

Thread overview: 36+ 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 [this message]
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
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
2006-04-18 15:07 ` Bastiaan Jacques

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=450763E4.6010602@gmail.com \
    --to=htejun@gmail.com \
    --cc=akpm@osdl.org \
    --cc=helge.hafting@aitel.hist.no \
    --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;
as well as URLs for NNTP newsgroup(s).