[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20110103222451.GA2959@thunk.org>
Date: Mon, 3 Jan 2011 17:24:51 -0500
From: Ted Ts'o <tytso@....edu>
To: Bjoern Slotkowski <bjoern.slotkowski@...-berlin.de>
Cc: Andreas Dilger <adilger.kernel@...ger.ca>,
linux-ext4@...r.kernel.org
Subject: Re: AW: Questions concerning ext2 filesystem: ext2_statfs
On Mon, Jan 03, 2011 at 02:12:04PM +0100, Bjoern Slotkowski wrote:
>
> But there is still one thing also in the newer kernel:
> f_bfree and f_ffree are determined by functions "ext2_count_free_blocks" and
> "ext2_count_free_inodes"
> which iterate through s_groups_count which needs a lot of time.
>
> When I look at ext3/super.c and ext4/super.c the member variables
> s_freeblocks_counter and s_freeinodes_counter are used directly in functions
> *_statfs.
>
> Probably there is potential for an optimization.
Perhaps, but note that ext4 is fully backwards compatible with ext2.
That is, you can mount ext2 file systems using the ext4 file system
driver. (You can also mount ext2 file systems using the ext3 file
system, although you will have to add a journal to the file system
first.)
Ext2 is primarily useful as an working, example file system which
shows how to interface a file system to Linux. As such piling in too
many optimizations isn't necessarily consistent with its current role.
No one is really actively maintaining ext2, except to update it work
with the latest kernel interfaces, so it's not clear who would do the
optimization.
If you want a faster, more efficient file system, there are plenty of
alternatives, including ext3 and ext4.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists