From: Andreas Dilger <adilger@clusterfs.com>
To: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Subject: Re: remove EXT2_MAX_BLOCK_SIZE
Date: Wed, 22 Jan 2003 14:12:42 -0700 [thread overview]
Message-ID: <20030122141242.K1594@schatzie.adilger.int> (raw)
In-Reply-To: <20030122202851.GR780@holomorphy.com>; from wli@holomorphy.com on Wed, Jan 22, 2003 at 12:28:51PM -0800
On Jan 22, 2003 12:28 -0800, William Lee Irwin III wrote:
> Remove 100% unused EXT2_MAX_BLOCK_SIZE.
>
> diff -urpN cleanup-2.5.59-3/include/linux/ext2_fs.h cleanup-2.5.59-4/include/linux/ext2_fs.h
> --- cleanup-2.5.59-3/include/linux/ext2_fs.h 2003-01-16 18:21:39.000000000 -0800
> +++ cleanup-2.5.59-4/include/linux/ext2_fs.h 2003-01-22 12:26:00.000000000 -0800
> @@ -90,7 +90,6 @@ static inline struct ext2_sb_info *EXT2_
> * Macro-instructions used to manage several block sizes
> */
> #define EXT2_MIN_BLOCK_SIZE 1024
> -#define EXT2_MAX_BLOCK_SIZE 4096
> #define EXT2_MIN_BLOCK_LOG_SIZE 10
> #ifdef __KERNEL__
> # define EXT2_BLOCK_SIZE(s) ((s)->s_blocksize)
Actually, the correct fix is to check in ext2_read_super() whether the
blocksize is larger than EXT2_MAX_BLOCK_SIZE like ext3 does, and maybe
even fix up the code drift between that part of ext2_read_super() and
ext3_read_super()...
Both ext2 and ext3 will in theory support a blocksize up to PAGE_SIZE,
but nobody with access to a > 4kB PAGE_SIZE system has bothered to test
whether it works, so EXT[23]_MAX_BLOCK_SIZE has not been increased.
Any e2fsprogs from the last year or so will support larger blocksizes,
but it has never been tested AFAIK.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2003-01-22 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 20:28 William Lee Irwin III
2003-01-22 21:12 ` Andreas Dilger [this message]
2003-01-22 21:15 ` William Lee Irwin III
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=20030122141242.K1594@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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®