linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 12 Mar 2010 10:37:20 +0900	[thread overview]
Message-ID: <4B999AD0.2090309@kernel.org> (raw)
In-Reply-To: <Pine.GSO.4.63.1003101012480.8035@galaxy.agh.edu.pl>

Hello,

On 03/10/2010 06:40 PM, Tomasz Palac wrote:
>> By solving the equations matching CHSs and LBAs.  It only works if the
>> first partition ends before the CHS address limit (2 variables to
>> solve for so we need 2 different equations).
> 
> Thanks for explanation. So with 64/32 geometry this should work for
> partitions smaller than 1 GiB. With 255/63 geometry this limit is 8 GiB
> and there are partitions bigger than that. Maybe for bigger partitions
> BIOSes use ending CHS?

I suspect more BIOSs would just assume 255/63 regardless of the
partition layout these days.  For bigger partitions, the ending CHS is
just a marker saying that it's off the limit and there really isn't
any information to calculate from.

>> The only reason we're talking about geometry is for compatibility w/
>> older operating systems.  So, at this point, diddling with geometry
>> just doesn't make any sense at all.
> 
> If we "do as Windows do" and make partitions aligned at 1 MiB but not
> aligned at cylinder boundary, then there is no way to boot Windows 2000
> or older OS. If we use 64/32 geometry, there is a chance (maybe small)
> that BIOS will calculate or assume correct CHS values and older OS can
> boot. And this geometry cannot hurt newer OSes.

Going forward, I think it would be simply better and less painful to
stick to the simpler scheme which is also employed by Windows and
allowing some way to use the old alignment for certain partitions for
those few special cases where really old OSs need to be used.  The
benefit of 64/32 or any other custom geometry seems marginal at best
and mostly imaginary to me.

Thanks.

-- 
tejun

      reply	other threads:[~2010-03-12  1:37 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
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 [this message]

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=4B999AD0.2090309@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).