From: Linus Torvalds <torvalds@transmeta.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Jens Axboe <axboe@suse.de>, <linux-kernel@vger.kernel.org>,
<jmerkey@timpanogas.org>
Subject: Re: Block I/O Enchancements, 2.5.1-pre2
Date: Tue, 27 Nov 2001 19:38:48 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.33.0111271933100.1195-100000@penguin.transmeta.com> (raw)
In-Reply-To: <3C044CB1.62F5650F@mandrakesoft.com>
On Tue, 27 Nov 2001, Jeff Garzik wrote:
>
> Oh yeah, I meant to ask: do we get 64-bit inode numbers and 64-bit block
> numbers on x86 sometime in 2.5?
Well, the 64-bit sector number skeleton is already there in pre2..
We will probably _not_ get 64-bit page index numbers, though. I don't want
to make the page structure bigger/slower for very little gain. So the page
cache is probably going to be limited to about 44 bits (45+ if people
start doing large pages, which is probably worth it). So there would still
be partition/file limits on the order of 16-64 TB in the next few years.
(In a longer timeframe, assuming RAM keeps getting cheaper and cheaper,
and 64-bit computing starts hppening on PC's, a few years down the line we
can re-visit this - that particular transition is not going to be too
painful).
And yes, I realize that you can already build big arrays and use LVM etc
to make them be more than 16TB. I just do not think it's a problem yet,
and I'd rather cater to "normal" people than to peopel who can't bother
to partition their data at all.
Linus
next prev parent reply other threads:[~2001-11-28 3:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-27 20:44 2.5.1-pre2 does not compile f5ibh
2001-11-27 20:50 ` Linus Torvalds
2001-11-27 22:09 ` Christoph Hellwig
2001-11-27 22:22 ` onboard ethernet/sound on Soyo SY-K7V? Dax Kelson
2001-11-27 22:47 ` François Cami
2001-11-27 22:57 ` Jeff Garzik
2001-11-27 22:29 ` 2.5.1-pre2 does not compile Robert Love
2001-11-28 0:29 ` Linus Torvalds
2001-11-28 12:55 ` Christoph Hellwig
2001-11-28 16:26 ` Andreas Dilger
2001-11-28 16:42 ` Christoph Hellwig
2001-11-28 16:39 ` Martin Dalecki
2001-11-28 17:27 ` Andreas Dilger
2001-11-28 0:40 ` Andre Hedrick
2001-11-27 22:02 ` Paul Mackerras
2001-11-28 1:04 ` Linus Torvalds
2001-11-28 1:34 ` Block I/O Enchancements, 2.5.1-pre2 Jeff V. Merkey
2001-11-28 1:45 ` Jeff Garzik
2001-11-28 1:55 ` Jeff V. Merkey
2001-11-28 2:32 ` Jeff Garzik
2001-11-28 3:38 ` Linus Torvalds [this message]
2001-11-30 2:19 ` Daniel Phillips
2001-11-30 12:21 ` Hans Reiser
[not found] ` <15367.32910.275973.287742@laputa.namesys.com>
2001-12-01 9:31 ` [reiserfs-dev] " Hans Reiser
2001-11-28 10:17 ` Martin Dalecki
2001-11-28 13:35 ` Jens Axboe
2001-11-28 17:29 ` Jeff Merkey
2001-11-28 6:58 ` 2.5.1-pre2 does not compile Jens Axboe
2001-11-28 12:20 ` bio write-up (was: Re: 2.5.1-pre2 does not compile) Jens Axboe
2001-11-29 1:07 ` 2.5.1-pre2 bio offset by one error in VIA IDE Anton Altaparmakov
2001-11-28 23:31 ` Anton Altaparmakov
2001-11-28 23:55 ` Andreas Dilger
2001-11-30 1:53 ` 2.5.1-pre2 does not compile Daniel Phillips
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=Pine.LNX.4.33.0111271933100.1195-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=axboe@suse.de \
--cc=jgarzik@mandrakesoft.com \
--cc=jmerkey@timpanogas.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).