From: Christoph Hellwig <hch@infradead.org>
To: Peter Chubb <peter@chubb.wattle.id.au>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com,
axboe@suse.de, akpm@zip.com.au, martin@dalecki.de,
neilb@cse.unsw.edu.au
Subject: Re: [PATCH] remove 2TB block device limit
Date: Mon, 13 May 2002 13:13:39 +0100 [thread overview]
Message-ID: <20020513131339.A4610@infradead.org> (raw)
In-Reply-To: <1060250300@toto.iv> <15583.38222.512544.921796@wombat.chubb.wattle.id.au>
On Mon, May 13, 2002 at 08:28:30PM +1000, Peter Chubb wrote:
>
> There's now a patch available against 2.5.15, and the BK repository
> has been updated to v2.5.15 as well:
>
> http://www.gelato.unsw.edu.au/patches/2.5.15-largefile-patch
> bk://gelato.unsw.edu.au:2023/
This looks really good, I'd like to see something like that merged soon!
Some comments:
- please move the sector_t typedef from <linux/types.h> to <asm/types.h>,
so 64 bit arches don't have to have the CONFIG_ option at all, some
32bit plattforms that are unlikely to ever support large disks
(m68k comes to mind) can make it 32bit unconditionally and some like
i386 can use a config option.
- sector_div should move to a common header (blkdev.h?)
And something related to general sector_t usage:
- what about sector_t vs daddr_t? Linux still has daddr_t, but it is
still always 32bit, I think a big s/sector_t/daddr_t/ would fit the
traditional unix way of doing disk addressing
- why is the get_block block argument a sector_t? It presents a logical
filesystem block which usually is larger than the sector, not to
mention that for the usual blocksize == PAGE_SIZE case a ulong is
enough as that is the same size the pagecache limit triggers.
next prev parent reply other threads:[~2002-05-13 12:13 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1060250300@toto.iv>
2002-05-13 10:28 ` Peter Chubb
2002-05-13 12:13 ` Christoph Hellwig [this message]
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
[not found] <581856778@toto.iv>
2002-05-17 0:04 ` Peter Chubb
2002-05-17 0:18 ` Daniel Phillips
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
-- 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=20020513131339.A4610@infradead.org \
--to=hch@infradead.org \
--cc=akpm@zip.com.au \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
--cc=neilb@cse.unsw.edu.au \
--cc=peter@chubb.wattle.id.au \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®