From: Alexandre Ratchov <alexandre.ratchov@bull.net>
To: linux-ext4@vger.kernel.org
Cc: Jean-Pierre Dion <jean-pierre.dion@bull.net>
Subject: rfc: 2fsprogs update
Date: Tue, 26 Sep 2006 16:33:43 +0200 [thread overview]
Message-ID: <20060926143343.GA20020@openx1.frec.bull.fr> (raw)
hello,
i've updated e2fsprogs to be in sync with the latest kernel changes; here is
a summary of all changes:
01-head_20060918
this is a diff between 1.39 and a mercurial snapshot from sep 18,
2006. It's here just to allow people to apply the patch set on
e2fsprogs-1.39
02-percent
fixes division by zero in e2p_percent(), already posted few days ago
The following are the patches that Andreas posted, no changes:
03-inode_prealloc
04-extents
05-extents_htree
06-eacheck
The following are for 64bit support; they do the same as the patch set i
posted the last time but with various bugs fixed; they are reorganised and
cleaned up:
07-pblk_ondisk_blocknum
convert all 32bit on-disk block number definitions (currently __u32,
blk_t, unsigned long, unsigned int...) to pblk_t that is defined as
__u32. In this way we are sure that blk_t is used only in memory.
Later, this would allow to make blk_t 64bit without disturbing any
programs (this would just eat more momory and use 64bit arithmetic).
08-use_64bit_io
use 64bit offsets and block numbers (unsigned long long) in
*_read_blk, *_write_blk, and friends.
09-use_64bit_block_numbers
add the 64BIT incompat feature (make blk_t 64bit and add "_hi" bits
un super block and descruptors)
10-extents_48bit_block_numbers
makes extents code use *_hi bits: updated according Andreas'
comments.
11-desc_size
allow larger block group descriptors. The in memory ext2_group_desc
structure can have an arbitrary size (the on-disk on still have to
be a power of 2). This change is necessary in order to enlarge block
groups later.
12-move_block_number_hi_bits
moves group descriptors "*_hi" bits to the larger part of the
ext2_group_desc structure.
I've successfully tested them on a x84_64 arch with a 20TB device with the
latest kernel patches.
The complete e2fsprogs and kernel patch sets are available here:
http://www.bullopensource.org/ext4/20060926/
Comments?
-- Alexandre
next reply other threads:[~2006-09-26 14:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 14:33 Alexandre Ratchov [this message]
2006-09-26 14:45 ` [patch 02/12] rfc: 2fsprogs update Alexandre Ratchov
2006-09-26 14:46 ` [patch 03/12] " Alexandre Ratchov
2006-09-26 14:47 ` [patch 04/12] " Alexandre Ratchov
2006-09-26 17:32 ` Theodore Tso
2006-09-26 19:54 ` Andreas Dilger
2006-09-26 21:16 ` Theodore Tso
2006-09-27 12:59 ` Alexandre Ratchov
2006-09-27 14:10 ` Theodore Tso
2006-09-26 14:47 ` [patch 05/12] " Alexandre Ratchov
2006-09-26 14:48 ` [patch 06/12] " Alexandre Ratchov
2006-09-26 14:48 ` [patch 07/12] " Alexandre Ratchov
2006-09-26 17:37 ` Theodore Tso
2006-09-27 13:36 ` Alexandre Ratchov
2006-09-27 14:38 ` Theodore Tso
2006-09-26 14:49 ` [patch 08/12] " Alexandre Ratchov
2006-09-26 14:50 ` [patch 10/12] " Alexandre Ratchov
2006-09-26 14:50 ` [patch 11/12] " Alexandre Ratchov
2006-09-26 14:50 ` [patch 12/12] " Alexandre Ratchov
2006-09-26 16:47 ` Alexandre Ratchov
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=20060926143343.GA20020@openx1.frec.bull.fr \
--to=alexandre.ratchov@bull.net \
--cc=jean-pierre.dion@bull.net \
--cc=linux-ext4@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