From: Valdis.Kletnieks@vt.edu
To: alex.buell@munted.org.uk
Cc: Tejun Heo <tj@kernel.org>, Jeff Garzik <jeff@garzik.org>,
ben.collins@ubuntu.com,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
hmh@debian.org
Subject: Re: support for drives larger than 2TiB
Date: Sat, 24 Jul 2010 09:49:08 -0400 [thread overview]
Message-ID: <92061.1279979348@localhost> (raw)
In-Reply-To: Your message of "Sat, 24 Jul 2010 13:36:06 BST." <1279974966.11927.26.camel@lithium.local.net>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
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.. ;)
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?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2010-07-24 13:51 UTC|newest]
Thread overview: 20+ 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 [this message]
2010-07-24 21:15 ` Alex Buell
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=92061.1279979348@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=alex.buell@munted.org.uk \
--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