linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/5] Forking ext4 filesystem and JBD2
Date: Wed, 09 Aug 2006 18:16:37 -0700	[thread overview]
Message-ID: <1155172597.3161.72.camel@localhost.localdomain> (raw)

This series of patch forkes a new filesystem, ext4, from the current
ext3 filesystem, as the code base to work on, for the big features such
as extents and larger fs(48 bit blk number) support, per our discussion
on lkml a few weeks ago. 

[patch 1/5] ext4-fork.patch
1) create a ext4 dir under fs/
2) copy all ext3 files to fs/ext4
3) rename all ext3/EXT3 symbols in ext4 filesystem source code to
ext4/EXT4 correspondingly.

[patch 2/5] register-ext3dev.patch
Registered the ext4 filesystem as ext3dev at this moment, as Ted Tso has
proposed before.  The intention is to explicitly tell the new filesystem
is still under development. And it will be re-register itself as ext4
filesystem once the on-disk format changes are pretty much developed and
merged.

[patch 3/5] fork-jbd2.patch
Forking JBD2 from JBD at the same time forking ext4 filesystem, as we
discussed before. New JBD2 layer is only used by ext4 for now, and will
support both 64bit and 32 bit blk number.

[patch 4/5] jbd2-rename-funcs.patch
Rename all exported symbols in JBD2 layer with a jbd2_ prefix to
distinguish them from those symbols from JBD layer.

[patch 5/5] rename-jbd2-in-ext4.patch
Use JBD2 functions/header files in ext4 filesystem

Tested the changes on i386 machine(load ext4and jbd2 as module and also
tested as built-in). Able to mount ext3dev filesystem on an exisiting
ext3 filesystem, and survived a few hours fsx tests and tiobench tests. 

Patches against 2.6.18-rc4 kernel. Previous extents and 48bit ext3
patches are rebased to against ext4 filesystem, will send them out in
another thread.  The whole series of ext4 patches (including patches to
fork ext4 filesystem and patches to add extents and 48 bit blk number)
are avaible at
http://ext2.sourceforge.net/48bitext3/patches/latest/

Any comments? Could we add ext4/jbd2 to mm tree for a wider testing?

Thanks,
Mingming


             reply	other threads:[~2006-08-10  1:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10  1:16 Mingming Cao [this message]
2006-08-10  5:58 ` [PATCH 0/5] Forking ext4 filesystem and JBD2 Jeff Garzik
2006-08-10 16:33   ` Mingming Cao
2006-08-10 17:00     ` Andrew Morton
2006-08-14 21:44       ` Pavel Machek
2006-08-15 19:06         ` Jeff Garzik
2006-08-10 14:02 ` Michal Piotrowski
2006-08-10 15:15   ` Michal Piotrowski
     [not found]     ` <1155236801.3162.1.camel@localhost.localdomain>
2006-08-10 19:06       ` John McCutchan
2006-08-10 19:06       ` John McCutchan
2006-08-10 19:06       ` John McCutchan
     [not found]     ` <1156012970.9346.1.camel@localhost.localdomain>
2006-08-19 18:42       ` John McCutchan
2006-08-19 21:17         ` Michal Piotrowski
2006-08-19 18:42       ` John McCutchan
2006-08-19 18:42       ` John McCutchan

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=1155172597.3161.72.camel@localhost.localdomain \
    --to=cmm@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).