public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: Mike Eldridge <diz@cafes.net>,
	Marcelo Borges Ribeiro <marcelo@datacom-telematica.com.br>,
	linux-kernel@vger.kernel.org
Subject: Re: Filesize limit on SMBFS
Date: 24 Nov 2001 13:43:59 -0700	[thread overview]
Message-ID: <m1n11bzypc.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.42.0111231034330.15987-100000@boston.corp.fedex.com> <002801c1740f$7372f650$1300a8c0@marcelo> <20011123171157.Q21290@mail.cafes.net> <20011124031625.T2682@mea-ext.zmailer.org>
In-Reply-To: <20011124031625.T2682@mea-ext.zmailer.org>

Matti Aarnio <matti.aarnio@zmailer.org> writes:

> The 2.5 series may change the underlying block-device layer so that
> it can handle larger block devices than 2TB - the 64 bit machines can
> handle them, of course, but 32-bit i386 is a bit limited...

Definitely.  Right now the page cache on x86 has a limit (per file) of
2^32 * PAGE_SIZE == 2^32 * 2^12 = 2^44 = 16TB.  And I doubt that will
change.  x86 will be going 64bit in the next 2-3 years, at which point
I don't see it paying to push 32bit code into the larger data sizes.
Especially when we our limit is still 2 orders of magnitude larger
then the largest disk manufactured today.

Now the file size limit on x86 can be increased a little by increasing
the internal PAGE_SIZE for the page cache but that will only give us a
bit or two which really isn't significant.

Eric


  reply	other threads:[~2001-11-24 21:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22 18:53 Filesize limit on SMBFS Tyler BIRD
2001-11-22 19:23 ` Marcelo Borges Ribeiro
2001-11-22 19:57   ` Andreas Dilger
2001-11-23  2:35     ` Jeff Chua
2001-11-23 11:10       ` Marcelo Borges Ribeiro
2001-11-23 12:00         ` Jeff Chua
2001-11-23 23:11         ` Mike Eldridge
2001-11-23 23:19           ` war
2001-11-23 23:19           ` Andreas Dilger
2001-11-23 23:45             ` Mike Eldridge
2001-11-24  1:16           ` Matti Aarnio
2001-11-24 20:43             ` Eric W. Biederman [this message]
2001-11-26 18:27           ` Alan Cox
2001-11-23  2:49     ` Anton Altaparmakov
2001-11-23  3:27       ` Jeff Chua
2001-11-23  7:09         ` OGAWA Hirofumi
2001-11-24  9:08   ` Albert D. Cahalan
  -- strict thread matches above, loose matches on Subject: below --
2001-11-22  9:10 Petr Tite(ra
2001-11-22 12:10 ` Urban Widmark
2001-11-22 13:01   ` Petr Titera
2001-11-22 20:58     ` Urban Widmark
2001-11-22 13:21   ` Anton Altaparmakov

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=m1n11bzypc.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=diz@cafes.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@datacom-telematica.com.br \
    --cc=matti.aarnio@zmailer.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