public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Oliver S." <Follow.Me@gmx.net>
To: <linux-kernel@vger.kernel.org>
Subject: AW: Benefits from computing physical IDE disk geometry?
Date: Sun, 13 Apr 2003 01:10:05 +0200	[thread overview]
Message-ID: <000001c30148$a7d0add0$0200000a@kimba> (raw)
In-Reply-To: <001301c30145$5ff85fb0$6801a8c0@epimetheus>

> Any good SCSI drive knows the physical geometry of the disk and can
> therefore optimally schedule reads and writes.

 If the scheduler inside the OS can rely on the drive to have a linear
mapping it is implemented as a cyclical-scan scheduler, there is only
a little difference in the effectivity of the scheduling.

> 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.

 AFAIK the Seagate Barracudas implement first-party-dma, which is a
very lightweight implementation of command-queuing; with first-party
-dma, the CPU includes the adresses of where the data for a certain
request is read or written into the request-command so that when the
disk responds to a command, it sends this information back to the
controller. So this chip doesn't have to hold a list of outstanding
requests and their scattered adresses where the data is read from or
written to. Doesn't look very elegant, but that's just in line with
the cheap ATA-concepts.
 And the only controller-chips I'm aware of supporting this features
are the chips fom Silicon Image. But I think that sooner or later,
all SATA-chips will support it.


  reply	other threads:[~2003-04-12 22:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-12 22:46 Benefits from computing physical IDE disk geometry? Timothy Miller
2003-04-12 23:10 ` Oliver S. [this message]
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
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

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='000001c30148$a7d0add0$0200000a@kimba' \
    --to=follow.me@gmx.net \
    --cc=linux-kernel@vger.kernel.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