From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org
Subject: e2fsprogs-1.39-tyt3
Date: Mon, 30 Apr 2007 11:22:25 -0400 [thread overview]
Message-ID: <E1HiXhp-0002Fi-Mm@candygram.thunk.org> (raw)
Per last week's conference call, I've included an update of the
e2fsprogs patchset to support extents. It still needs more work before
it can be folded into mainline, but I'm including them so that people
can see which way I'm headed, and because debugfs has been enhaced to
show extents, which can be useful for developers.
One concern I still have is the fact that we're exposing a lot of
interfaces in libext2fs.so which are very specifically tied to the
current 48-bit physical/32-bit logical on-disk extent data structure.
If/when we add support for the 64/64-bit extent data structure, and some
kind of compressed/bit-packed extent format, those interfaces will have
to be extended.
Another problem is that while external extent blocks are getting byte
swapped, there is no byte swapping going on for the extents stored in
the inode. I haven't tried it on a big endian system, such as Power
machine, but I'm pretty sure it's going to blow up spectacularly.
The patches can be found at:
ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs-interim/e2fsprogs-1.39-tyt3
- Ted
next reply other threads:[~2007-04-30 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 15:22 Theodore Ts'o [this message]
2007-05-01 7:56 ` e2fsprogs-1.39-tyt3 Andreas Dilger
2007-05-01 15:05 ` e2fsprogs-1.39-tyt3 Theodore Tso
2007-05-01 18:49 ` e2fsprogs-1.39-tyt3 Andreas Dilger
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=E1HiXhp-0002Fi-Mm@candygram.thunk.org \
--to=tytso@mit.edu \
--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 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.