From: Alex Buell <alex.buell@munted.org.uk>
To: Tejun Heo <tj@kernel.org>
Cc: 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 13:36:06 +0100 [thread overview]
Message-ID: <1279974966.11927.26.camel@lithium.local.net> (raw)
In-Reply-To: <4C4AB952.9030705@kernel.org>
On Sat, 2010-07-24 at 11:58 +0200, Tejun Heo wrote:
> The only problem is that everything which is necessary for booting
> needs to be located below 2TiB limit. Please note that this is much
> stricter restriction than the 128GiB limit we had due to LBA28. That
> limit was caused by BIOSes using LBA28 and vendors could and did
> update and be done with it in many cases. However, 2TiB limit is
> inherent in the BIOS programming interface and currently the only way
> to overcome it is using a completely different BIOS interface (EFI,
> that is). Vendors are not likely to introduce EFI for already
> released products although they're much more likely to release updates
> so that BIOSes can access upto 2TiB if they don't work already. We'll
> be stuck with 2TiB limit on much more configurations for longer period
> of time.
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.
--
http://www.munted.org.uk
One very high maintenance cat living here.
next prev parent reply other threads:[~2010-07-24 12:36 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 [this message]
2010-07-24 13:49 ` Valdis.Kletnieks
2010-07-24 21:15 ` Alex Buell
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=1279974966.11927.26.camel@lithium.local.net \
--to=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