linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: Anton Altaparmakov <aia21@cantab.net>,
	Peter Chubb <peter@chubb.wattle.id.au>,
	Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org, axboe@suse.de, akpm@zip.com.au,
	martin@dalecki.de, neilb@cse.unsw.edu.au
Subject: Re: [PATCH] remove 2TB block device limit
Date: Fri, 17 May 2002 02:18:20 +0200	[thread overview]
Message-ID: <E178VRs-0008Va-00@starship> (raw)
In-Reply-To: <15588.18673.317088.198281@wombat.chubb.wattle.id.au>

On Friday 17 May 2002 02:04, Peter Chubb wrote:
> >>>>> "Daniel" == Daniel Phillips <phillips@bonn-fries.net> writes:
> 
> Daniel> On Tuesday 14 May 2002 03:36, Anton Altaparmakov wrote:
> >> ...And yes at the moment the pagecache limit is also a problem
> >> which we just ignore in the hope that the kernel will have gone to
> >> 64 bits by the time devices grow that large as to start using > 32
> >> bits of blocks/pages...
> 
> Daniel> PAGE_CACHE_SIZE can also grow, so 32 bit architectures are
> Daniel> further away from the page cache limit on than it seems.
> 
> Check out the table on page 2 of
> http://www.scsita.org/statech/01s005r1.pdf 
> 
> The SCSI trade association is predicting 200TB in a high-end server
> within 10 years --- and  2TB in a high-end desktop by 2004.  I'd take
> some of their predictions with a grain of salt, however.

The server definitely won't be running a 32 bit processor, and the high
end desktop probably won't.  In any event, the current 44 bit limitation
(32 bit arch) on the page cache takes us up to 16 TB, and going to a 16 KB 
PAGE_CACHE_SIZE takes us to 64 TB, so I don't think we have to start
slicing and dicing that part of the kernel just now.  Anybody who expects
to run into this limitation should of course raise their hand.

Incidently, the 200 TB high-end servers are a lot closer than you think.

-- 
Daniel

  reply	other threads:[~2002-05-17  0:19 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <581856778@toto.iv>
2002-05-17  0:04 ` [PATCH] remove 2TB block device limit Peter Chubb
2002-05-17  0:18   ` Daniel Phillips [this message]
2002-05-17 13:32     ` Jesse Pollard
2002-05-17 18:02       ` Daniel Phillips
2002-05-17 18:26         ` Jesse Pollard
2002-05-17 18:36       ` Andreas Dilger
2002-05-17 19:52       ` Daniel Phillips
2002-05-17 20:25         ` Andrew Morton
2002-05-17 15:26     ` Jason L Tibbitts III
2002-05-15  9:41 Hirotaka Sasaki
2002-05-15 21:49 ` Steve Lord
     [not found] <1060250300@toto.iv>
2002-05-13 10:28 ` Peter Chubb
2002-05-13 12:13   ` Christoph Hellwig
2002-05-14  0:30     ` Peter Chubb
2002-05-14  1:36       ` Anton Altaparmakov
2002-05-16 20:32         ` Daniel Phillips
2002-05-14  2:09       ` Andrew Morton
2002-05-14  2:58         ` Peter Chubb
2002-05-14  7:22           ` Christoph Hellwig
2002-05-14  7:21         ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2002-05-10  3:53 Neil Brown
2002-05-10  3:36 Peter Chubb
2002-05-10  4:05 ` Andrew Morton
2002-05-10  8:43   ` Anton Altaparmakov
2002-05-10  9:04     ` Andrew Morton
2002-05-16 19:08       ` Daniel Phillips
2002-05-10  9:05     ` Jens Axboe
2002-05-10  9:53       ` Peter Chubb
2002-05-10 10:01         ` Jens Axboe
2002-05-10 11:43         ` Anton Altaparmakov
2002-05-10  4:51 ` Martin Dalecki
     [not found] ` <20020510084713.43ce396e.jeremy@kerneltrap.org>
2002-05-10 19:12   ` Peter Chubb
2002-05-10 23:46     ` Andreas Dilger
2002-05-11  0:07       ` David Mosberger
2002-05-15 22:17         ` Andreas Dilger
2002-05-16 20:22           ` Daniel Phillips
2002-05-16 22:54             ` Andreas Dilger
2002-05-17  1:17               ` Daniel Phillips
2002-05-11  4:40       ` Peter Chubb
2002-05-15 13:49       ` Pavel Machek
2002-05-11 18:13     ` Padraig Brady

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=E178VRs-0008Va-00@starship \
    --to=phillips@bonn-fries.net \
    --cc=aia21@cantab.net \
    --cc=akpm@zip.com.au \
    --cc=axboe@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@dalecki.de \
    --cc=neilb@cse.unsw.edu.au \
    --cc=peter@chubb.wattle.id.au \
    /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).