Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Alex Buell <alex.buell@munted.org.uk>
To: Valdis.Kletnieks@vt.edu
Cc: ben.collins@ubuntu.com, Jeff Garzik <jeff@garzik.org>,
	Tejun Heo <tj@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	hmh@debian.org
Subject: Re: support for drives larger than 2TiB
Date: Sat, 24 Jul 2010 22:15:38 +0100	[thread overview]
Message-ID: <1280006138.11927.61.camel@lithium.local.net> (raw)
In-Reply-To: <92061.1279979348@localhost>

On Sat, 2010-07-24 at 09:49 -0400, Valdis.Kletnieks@vt.edu wrote:
> On Sat, 24 Jul 2010 13:36:06 BST, Alex Buell said:
> 
> > The only thing that would please me no end with newer replacements for
> > BIOS is the ability to have 4k boot sectors. Imagine what we can do with
> > 4k what we can't do with 512 bytes. 
> 
> Are you saying that 4K sectors have some special nice implications for the boot
> process, or that the boot process is the last major hangup to fully supporting
> a device with 4K sectors, which would give us an 8X boost in capacity on all
> the codepaths that work via sector humbers?  I suspect you mean the latter, but
> it's early in the morning  still.. ;)

It would be interesting to see how newer BIOSses cope with 4k boot
sectors. I'm sure the latest ATAPI standards do allow 4k boot sectors, I
just want to know how this will be implemented for devices with larger
physical sectors than the more usual 512 byte sectors. 

> As a side consideration - moving from 512 to 4K moves the associated limit from
> 2 TiB to 16 TiB.  Given the current rate of device density increase, how much
> time will that buy us, and what do we do then?

There are now 3TB devices out there. But noone can boot from 4k devices
yet on existing PC systems. 

I'm sure a market to provide 3rd party BIOSes able to do this will
develop shortly. I know of one: coreboot. 
-- 
http://www.munted.org.uk

One very high maintenance cat living here.

  reply	other threads:[~2010-07-24 21:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-24  9:58 support for drives larger than 2TiB Tejun Heo
2010-07-24 12:21 ` Henrique de Moraes Holschuh
2010-07-24 12:36 ` Alex Buell
2010-07-24 13:49   ` Valdis.Kletnieks
2010-07-24 21:15     ` Alex Buell [this message]
2010-07-24 23:08     ` Stan Hoeppner
2010-07-25  7:56       ` Tejun Heo
2010-07-25  8:05         ` Mikael Abrahamsson
2010-07-24 18:40 ` Yuhong Bao
2010-07-24 21:38   ` Greg Freemyer
2010-07-24 23:22     ` Henrique de Moraes Holschuh
2010-07-25  7:49       ` Tejun Heo
2010-07-25  2:25     ` Yuhong Bao
2010-07-25  8:01   ` Tejun Heo
2010-07-25  8:07     ` H. Peter Anvin
2010-07-25  8:20       ` Tejun Heo
2010-07-25 18:52         ` H. Peter Anvin
2010-07-27  8:41           ` Tejun Heo
2010-07-25  8:26       ` Alex Buell
2010-07-25 18:53         ` H. Peter Anvin
2010-07-24 18:48 ` Yuhong Bao
2010-08-19 13:12   ` Mark Lord
2010-08-23  7:40     ` Yuhong Bao

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=1280006138.11927.61.camel@lithium.local.net \
    --to=alex.buell@munted.org.uk \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=ben.collins@ubuntu.com \
    --cc=hmh@debian.org \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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