From: Mingming Cao <cmm@us.ibm.com>
To: akpm@osdl.org
Cc: linux-fsdevel@vger.kernel.org, ext2-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/9] extents and 48bit blk changes for ext4 filesystem
Date: Wed, 09 Aug 2006 18:19:57 -0700 [thread overview]
Message-ID: <1155172797.3161.79.camel@localhost.localdomain> (raw)
As we have forked the ext4 filesystem and JBD2, this is an update the
previously known as 48bit ext3 patches
changes since last time:
-rebase all previous ext3 patches to against ext4/jbd2
-fixed an reservation window intialization issue with extent block
allocation
and merge the change to the parent patch:ext4-extents.patch
-merged prevous bug fixes patches from sct for 64 jbd2 to their parent
patch:64bit-jbd2-core.patch
-merged ext3-extents-fsblk_t patch to ext4-extents-48bit.patch
-merged
64bit-incompat-flag-change.patch
ext3-sb-struc-sync-with-e2fsprog.patch
to parent patch
64bit-metadata.patch
A complete series of patches (including forking ext4 filesystem patches
and 48bit patches submitted here) could be found at:
http://ext2.sourceforge.net/48bitext3/patches/latest/
To test the new ext3dev filesystem, just mount the filesystem with -t
ext3dev. By default ext3dev is still running 32 bit mode and without
extents. To testing extents and 48bit block number, need -o extent mount
option. (Maybe we should enable extent as default for ext3dev
filesystem ?)
Tested these patches on i386 and passed a few hours fsx test.
Thanks,
Mingming
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
reply other threads:[~2006-08-10 1:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1155172797.3161.79.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).