public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Francis Moreau <francis.moro@gmail.com>
Cc: Seewer Philippe <philippe.seewer@bfh.ch>, linux-kernel@vger.kernel.org
Subject: Re: Disk geometry from /sys
Date: Tue, 22 Apr 2008 18:44:05 -0400	[thread overview]
Message-ID: <480E6A35.4040108@rtr.ca> (raw)
In-Reply-To: <38b2ab8a0804221316o7cab5641q16814849a1099b9a@mail.gmail.com>

Francis Moreau wrote:
> Hello Mark
> 
> On Fri, Apr 18, 2008 at 3:22 PM, Mark Lord <lkml@rtr.ca> wrote:
>>  That can sound a bit misleading.  The complete story, for ATA/SATA drives,
>>  is that the disk has two geometries:  an internal physical one, with a
>> fixed number of heads and cylinders, but variable sectors/track
>>  (which normally varies by cylinder zone).
>>
>>  Software *never* sees or knows about that geometry, so ignore it.
>>
>>  The second geometry, is the one that the drive reports to software
>>  as its "native" geometry.  This is what you see from "hdparm -I"
>>  and friends, and this geometry is what has to be used by software
>>  when using cylinder/head/sector (CHS) addressing for I/O operations.
>>  The hardware interface has a limit of 4-bits for the head value,
>>  so the maximum number of heads can never be more than 16.
>>
>>  Nobody uses CHS addressing for I/O operations, at least not on
>>  any hardware newer than at least ten years old, so this geometry
>>  is also unimportant for most uses.
>>
> 
> Is it because IDE drives support several IO operation modes ?
..

The earliest IDE drives for Compaq used only CHS sector addressing mode.

Within four years, though, all new drives had support for the more 
sensible linear block addressing (LBA) mode, as well.

LBA has been mandatory in new drives since the early 1990s,
so there's really no point to CHS addressing any more,
except when fiddling with MS-DOS style partition tables
(which have both CHS and LBA values stored inside).

Cheers

  reply	other threads:[~2008-04-22 22:44 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09 20:53 Disk geometry from /sys Francis Moreau
2008-04-09 21:28 ` Lennart Sorensen
2008-04-09 21:52   ` Alan Cox
2008-04-09 22:16   ` Bernd Eckenfels
2008-04-10 14:52     ` Lennart Sorensen
2008-04-10 19:23   ` Francis Moreau
2008-04-09 21:57 ` Mark Lord
2008-04-10 19:05   ` Francis Moreau
2008-04-10 19:53     ` Mark Lord
2008-04-10 12:22 ` linux-os (Dick Johnson)
2008-04-10 19:15   ` Francis Moreau
2008-04-10 13:58 ` Bill Davidsen
2008-04-14 12:57 ` Seewer Philippe
2008-04-15  7:40   ` Francis Moreau
2008-04-16  7:49     ` Seewer Philippe
2008-04-17 14:09       ` Francis Moreau
2008-04-17 14:49         ` Seewer Philippe
2008-04-18 13:22           ` Mark Lord
2008-04-18 13:37             ` Seewer Philippe
2008-04-22 20:11               ` Francis Moreau
2008-04-23  6:44                 ` Seewer Philippe
2008-04-23  6:56                   ` Francis Moreau
2008-04-22 20:16             ` Francis Moreau
2008-04-22 22:44               ` Mark Lord [this message]
2008-04-23  6:53                 ` Seewer Philippe
2008-04-23  7:02                 ` Francis Moreau
2008-04-23  9:33                   ` Seewer Philippe
2008-04-23 13:47                   ` Mark Lord
2008-04-22 20:10           ` Francis Moreau
2008-04-23  6:48             ` Seewer Philippe

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=480E6A35.4040108@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=francis.moro@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philippe.seewer@bfh.ch \
    /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