From: Seewer Philippe <philippe.seewer@bfh.ch>
To: Mark Lord <lkml@rtr.ca>
Cc: Francis Moreau <francis.moro@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Disk geometry from /sys
Date: Fri, 18 Apr 2008 15:37:13 +0200 [thread overview]
Message-ID: <4808A409.3080406@bfh.ch> (raw)
In-Reply-To: <4808A09B.6090106@rtr.ca>
Mark Lord 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.
>
> That's what the drive knows about.
>
> Software, for compatibility with the MS-DOS partition table scheme,
> sometimes uses a "logical" geometry, where we "pretend" that a drive
> can have up to 255 heads, which then allows more of the disk to be
> described within the limitations of the partition table data layout.
> That's where one frequently sees "255 heads", even though the drive
> underneath uses 16 at the interface level, and probably as only 2
> or 4 real heads inside the shell.
Aye. Though I prefer the term virtual geometry. But thats cosmetics.
Sorry for beeing unclear, and many thanks for untangling my post.
If anyones interested in even more Details about C/H/S adressing and so
on, there's a very good document about that to be found here:
http://www.mossywell.com/boot-sequence/
next prev parent reply other threads:[~2008-04-18 13:37 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 [this message]
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
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=4808A409.3080406@bfh.ch \
--to=philippe.seewer@bfh.ch \
--cc=francis.moro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.