mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Timothy Miller <tmiller10@cfl.rr.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Benefits from computing physical IDE disk geometry?
Date: 13 Apr 2003 15:29:34 +0100	[thread overview]
Message-ID: <1050244174.24187.15.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <001301c30145$5ff85fb0$6801a8c0@epimetheus>

On Sad, 2003-04-12 at 23:46, Timothy Miller wrote:
> Any good SCSI drive knows the physical geometry of the disk and can
> therefore optimally schedule reads and writes.  Although necessary features,
> like read queueing, are also available in the current SATA spec, I'm not
> sure most drives will implement it, at least not very well.

Some of them are in recent PATA and Jens Axboe implemented the TCQ for
IDE, but its all a bit limited right now

> So, what if one were to write a program which would perform a bunch of
> seek-time tests to estimate an IDE disk's physical geometry?  It could then
> make that information available to the kernel to use to reorder accesses
> more optimally.

Its a common misconception that a disk looks something like it did 15
years ago. Your ATA disk is basically an entire standalone computer 
running a small OS. The physical disk layout does not divide neatly 
into equal sized cylinders and some blocks may even be in suprising
places due to bad block sparing or anything else the drive manufacturer
felt appropriate.

The drive firmware will look after a lot of the optimising for you,
and once it gets TCQ it will probably get you all you want from SCSI
with SATA. Until then playing games with it isnt likely to help - feed
IDE disks large, sequential I/O as much as possible and they'll deliver
you very nice numbers. 

Alan


  parent reply	other threads:[~2003-04-13 15:16 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-12 22:46 Timothy Miller
2003-04-12 23:10 ` AW: " Oliver S.
2003-04-13  9:51 ` John Bradford
2003-04-13 11:50 ` Nick Piggin
2003-04-13 15:25   ` Timothy Miller
2003-04-14  3:52     ` Nick Piggin
2003-04-14  6:44       ` Mark Hahn
2003-04-14 13:28         ` Nick Piggin
2003-04-13 14:29 ` Alan Cox [this message]
2003-04-13 16:15   ` John Bradford
2003-04-18 13:01     ` Helge Hafting
2003-04-18 13:25       ` John Bradford
2003-04-14 18:27 ` Wes Felter
2003-04-13 18:03 Chuck Ebbert
2003-04-13 18:24 ` Dr. David Alan Gilbert
2003-04-13 18:32   ` Lars Marowsky-Bree
2003-04-13 18:51     ` Dr. David Alan Gilbert
2003-04-13 22:14   ` Alan Cox
2003-04-14  0:17     ` Andreas Dilger
2003-04-13 22:15 ` Alan Cox
2003-04-14  3:58   ` Nick Piggin
2003-04-13 22:13 Chuck Ebbert
2003-04-13 23:38 ` Andreas Dilger
2003-04-14  2:29 Chuck Ebbert
2003-04-14  3:44 Chuck Ebbert
2003-04-14 21:27 Chuck Ebbert
2003-04-15  0:03 ` Nick Piggin
2003-04-15  1:19 Chuck Ebbert
2003-04-15  8:28 ` Nick Piggin
2003-04-15 18:33 Chuck Ebbert
2003-04-16  1:16 ` Nick Piggin
2003-04-16  1:59   ` Nick Piggin
2003-04-16 13:28 Chuck Ebbert
2003-04-16 23:06 ` Nick Piggin

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=1050244174.24187.15.camel@dhcp22.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmiller10@cfl.rr.com \
    /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

all inboxes | Powered by JetHome®