From: Tejun Heo <tj@kernel.org>
To: Tomasz Palac <palac@uci.agh.edu.pl>
Cc: linux-ide@vger.kernel.org
Subject: Re: Comment on ATA 4 KiB sector issues
Date: Wed, 10 Mar 2010 14:46:38 +0900 [thread overview]
Message-ID: <4B97323E.1040807@kernel.org> (raw)
In-Reply-To: <Pine.GSO.4.63.1003090947570.29136@galaxy.agh.edu.pl>
Hello,
On 03/09/2010 06:22 PM, Tomasz Palac wrote:
>> Using custom geometry is a good way to trick a partitioner which
>> partitions based on CHS alignment to align to larger units but it
>> isn't meaningful outside of that. If CHS dosen't follow 255*63, a lot
>> of code (firmware, BIOS, boot loader, OS...) will just assume CHS is
>> incorrect.
>
> As of firmware, Large Disk Howto states that a lot of SCSI host
> adapters are using 64/32 geometry (at least for disks smaller than 8
> GiB). If BIOS supports EDD (INT13h Extensions), then disk geometry
> is irrelevant.
Yes, the geometry is basically arbitrary values which can be queried
using a BIOS call and the reason why SCSI hosts can choose them is
they implement BIOS extensions themselves.
> If not, then geometry can be read from partition table.
>From where?
> The only problem with 64/32 geometry is 1 GiB (as opposed to 8 GiB)
> limit for boot partition (without using EDD). The same applies to
> boot loaders. Modern OSes don't use CHS.
For modern OSes, geometry doesn't matter at all. Older ones are the
ones having problems (I've been corrected: XP seems okay while 2000
depends on CHS).
Thanks.
--
tejun
next prev parent reply other threads:[~2010-03-10 5:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.63.1003080933100.4114@galaxy.agh.edu.pl>
[not found] ` <4B95AEF6.8030906@kernel.org>
2010-03-09 9:22 ` Comment on ATA 4 KiB sector issues Tomasz Palac
2010-03-10 5:46 ` Tejun Heo [this message]
2010-03-10 8:15 ` Tomasz Palac
2010-03-10 8:33 ` Tejun Heo
2010-03-10 9:40 ` Tomasz Palac
2010-03-12 1:37 ` Tejun Heo
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=4B97323E.1040807@kernel.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=palac@uci.agh.edu.pl \
/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.