From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Alex Tomas <alex@clusterfs.com>,
Andreas Dilger <adilger@clusterfs.com>,
Mingming Cao <cmm@us.ibm.com>,
Avantika Mathur <mathur@linux.vnet.ibm.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: new mballoc patches.
Date: Tue, 11 Sep 2007 13:59:26 +0530 [thread overview]
Message-ID: <46E651E6.3070107@linux.vnet.ibm.com> (raw)
I have updated the mballoc patches. The same can be found at
http://www.radian.org/~kvaneesh/ext4/patch-series/
The series file is
# This series applies on GIT commit b07d68b5ca4d55a16fab223d63d5fb36f89ff42f
ext4-journal_chksum-2.6.20.patch
ext4-journal-chksum-review-fix.patch
ext4_uninit_blockgroup.patch
64-bit-i_version.patch
i_version_hi.patch
ext4_i_version_hi_2.patch
i_version_update_ext4.patch
jbd-stats-through-procfs
jbd-stats-through-procfs_fix.patch
delalloc-vfs.patch
delalloc-ext4.patch
ext-truncate-mutex.patch
ext3-4-migrate.patch
new-extent-function.patch
generic-find-next-le-bit
mballoc-core.patch
ext234_enlarge_blocksize.patch
ext2_rec_len_overflow_with_64kblk_fix.patch
ext3_rec_len_overflow_with_64kblk_fix.patch
ext4_rec_len_overflow_with_64kblk_fix.patch
RFC-1-2-JBD-slab-management-support-for-large-b.patch
RFC-2-2-JBD-blocks-reservation-fix-for-large-bl.patch
Changes:
a) deleted mballoc-fixup.patch; merged with mballoc-core.path
b) deleted mballoc-mkdir-oops-fix.patch; merged with mballoc-core.patch
c) merged Uninitialized group related changes for mballoc
d) merged the checkpatch.pl error fix patch for mballoc
e) merged the fix for ext4_ext_search_right for error
EXT4-fs error (device sdc): ext4_ext_search_right: bad header in inode #3745797: unexpected eh_depth - magic f30a, entries 81, max 84(0), depth 0(1)
f) PPC build fix by introducing generic_find_next_le_bit()
g) Document the code. Rest of the places that needs more comments are marked with FIXME!!
h) 48 bit block usage by converting bg_*_bitmap and bg_inode_table to respective ext4_*_bitmap and ext4_inode_table() function
i) Added jbd fixes patches from Mingming for large block size with the comment from hch. (this is added towards the end of the series)
k) Updated the ext234_enlarge_blocksize.patch ext2_rec_len_overflow_with_64kblk_fix.patch ext3_rec_len_overflow_with_64kblk_fix.patch
ext4_rec_len_overflow_with_64kblk_fix.patch to make sure they can be applied with stgit. They didn't had a valid email id in the
From: field. ( This is only commit message update )
Test status:
Minor testing with KVM. I also didn't do a PPC build.
Mingming/Avantika,
Can we update the patch queue with the series ?
-aneesh
next reply other threads:[~2007-09-11 8:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 8:29 Aneesh Kumar K.V [this message]
2007-09-11 15:04 ` new mballoc patches Aneesh Kumar K.V
[not found] ` <46E7DF34.8090209@bull.net>
2007-09-12 17:59 ` Aneesh Kumar K.V
2007-09-13 0:30 ` Mingming Cao
2007-09-11 23:18 ` Mingming Cao
2007-09-13 2:51 ` Aneesh Kumar K.V
2007-09-14 12:10 ` Aneesh Kumar K.V
2007-09-30 3:51 ` Alex Tomas
2007-09-27 5:58 ` Andrew Morton
2007-09-27 6:33 ` Aneesh Kumar K.V
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=46E651E6.3070107@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@clusterfs.com \
--cc=alex@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mathur@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).