From: Theodore Tso <tytso@valinux.com>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: Alexander Viro <viro@math.psu.edu>,
tytso@valinux.com, linux-kernel@vger.kernel.org,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Ext2 development mailing list <ext2-devel@lists.sourceforge.net>
Subject: Re: [Ext2-devel] ext2 inode size (on-disk)
Date: Fri, 20 Apr 2001 02:37:39 -0400 [thread overview]
Message-ID: <20010420023739.E5417@think> (raw)
In-Reply-To: <Pine.GSO.4.21.0104192213060.19860-100000@weyl.math.psu.edu> <200104200535.f3K5Ze82017093@webber.adilger.int>
In-Reply-To: <200104200535.f3K5Ze82017093@webber.adilger.int>; from adilger@turbolinux.com on Thu, Apr 19, 2001 at 11:35:40PM -0600
On Thu, Apr 19, 2001 at 11:35:40PM -0600, Andreas Dilger wrote:
> I don't _think_ that there is a requirement for a multiple-of-8 inodes
> per group. OK, looking into mke2fs (actually lib/ext2fs/initialize.c)
> it _does_ show that it needs to be a multiple of 8, but I'm not sure
> exactly what the "bitmap splicing code" mentioned in the comment is.
It's has to be a multiple of 8 because of how e2fsprogs handles
bitmaps --- that is, it takes the various pieces of all of the
bitmaps, and butts them up together in memory. It would be possible
to remove this restriction by reworking the e2fsprogs library code,
but quite frankly, I don't think the restriction is all that
unreasonable.
- Ted
next prev parent reply other threads:[~2001-04-20 6:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001202014045.F2272@parcelfarce.linux.theplanet.co.uk>
2001-04-19 11:55 ` ext2 inode size (on-disk) Alexander Viro
2001-04-19 17:41 ` Andreas Dilger
2001-04-19 18:02 ` Alexander Viro
2001-04-19 19:24 ` Andreas Dilger
2001-04-20 2:12 ` Alexander Viro
2001-04-19 20:10 ` [Ext2-devel] " tytso
2001-04-19 20:29 ` Jeff Garzik
2001-04-20 6:30 ` Theodore Tso
2001-04-20 2:23 ` Alexander Viro
2001-04-20 5:35 ` Andreas Dilger
2001-04-20 6:37 ` Theodore Tso [this message]
2001-04-20 6:35 ` Theodore Tso
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=20010420023739.E5417@think \
--to=tytso@valinux.com \
--cc=adilger@turbolinux.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@math.psu.edu \
/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