linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Andreas Dilger <adilger@sun.com>
Cc: linux-fsdevel@vger.kernel.org, dm-devel@redhat.com,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: How to handle >16TB devices on 32 bit hosts ??
Date: Wed, 22 Jul 2009 11:51:55 -0700	[thread overview]
Message-ID: <20090722115155.f99dcf76.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090722183244.GO4231@webber.adilger.int>

On Wed, 22 Jul 2009 12:32:44 -0600
Andreas Dilger <adilger@sun.com> wrote:

> On Jul 21, 2009  23:59 -0700, Andrew Morton wrote:
> > On Sat, 18 Jul 2009 10:08:10 +1000 Neil Brown <neilb@suse.de> wrote:
> > I expect that the VFS could be made to work with 64-bit pgoff_t fairly
> > easily.  The generated code will be pretty damn sad.
> > 
> > radix-trees use a ulong index, so we would need a new
> > lib/radix_tree64.c or some other means of fixing that up.
> > 
> > The bigger problem is filesystems - they'll each need to be checked,
> > tested, fixed and enabled.  It's probably not too bad for the
> > mainstream filesystems which mostly bounce their operations into VFS
> > libarary functions anyway.
> 
> I don't think this is a primary concern for most filesystems even today.
> Filesystems that work correctly > 16TB on 64-bit platforms should continue
> to work correctly on 32-bit platforms.

Not if they use an unsigned long to hold a pagecache index anywhere.

akpm:/usr/src/25> grep 'unsigned long' fs/*/*.c | wc -l
3465

      reply	other threads:[~2009-07-22 18:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18  0:08 How to handle >16TB devices on 32 bit hosts ?? Neil Brown
2009-07-18  4:31 ` Andreas Dilger
2009-07-18  6:16   ` Andi Kleen
2009-07-18  6:52     ` Andreas Dilger
2009-07-18  7:48       ` Andi Kleen
2009-07-18 13:49         ` Theodore Tso
2009-07-18 14:21           ` Andi Kleen
2009-07-18 14:32             ` Andreas Dilger
2009-07-18 18:19             ` Christoph Hellwig
2009-07-29 15:07           ` Pavel Machek
2009-07-19  3:44         ` Tapani Tarvainen
2009-07-18  6:09 ` Andi Kleen
2009-07-22  6:59 ` Andrew Morton
2009-07-22 18:32   ` Andreas Dilger
2009-07-22 18:51     ` Andrew Morton [this message]

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=20090722115155.f99dcf76.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adilger@sun.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@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).