From: Valerie Clement <valerie.clement@bull.net>
To: Theodore Tso <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: [RFC][PATCH 0/12] e2fsprogs: add 64-bit support
Date: Mon, 11 Jun 2007 18:41:56 +0200 [thread overview]
Message-ID: <466D7B54.7050005@bull.net> (raw)
Hi Ted,
Here is the new version of our e2fsprogs patches to add the 64-bit
support in the e2fsprogs tools.
First, I introduced a new compilation option to build e2fsprogs
utilities for ext4 filesytems and not break backwards compatiblity with
ext2/3 filesystems.
So most of the new code for ext4 is included under #ifdef _EXT4FS_.
The major change is that when compiling with _EXT4FS_ option, blk_t is
64 bits.
I tried to create new interfaces for ext4 which use the new type blk64_t
you defined, so most of the code in the patches 03 and 05 are simply
duplicated from the 32-bit version.
This patchset is also not complete:
TODO:
- support of 48-bit in extents to complete,
- support of 48-bit block number for ACL to do,
- change the format string %u for a block number to %llu in case of
64 bits (many occurences in the code),
- update code under ext2ed/,
- and surely other utilities/interfaces I don't use or know to port.
Code compiled, booted and briefly tested on a 20TB device (mkfs,
debugfs, e2fsck, dumpe2fs, filefrag tested)
Some non-regression tests also done on ext3 filesystems when compiling
code without _EXT4FS_ option.
I splitted the changes into 12 patches to facilitate the review of the
patches. I hope this work will be able to make progress on the code for
the 64-bit support.
Valérie
next reply other threads:[~2007-06-11 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 16:41 Valerie Clement [this message]
2007-06-11 23:12 ` [RFC][PATCH 0/12] e2fsprogs: add 64-bit support Andreas Dilger
2007-06-12 11:25 ` Valerie Clement
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=466D7B54.7050005@bull.net \
--to=valerie.clement@bull.net \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.