From: Alex Tomas <alex@clusterfs.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Design alternatives for fragments/file tail support in ext4
Date: Sat, 02 Dec 2006 14:02:53 +0300 [thread overview]
Message-ID: <m33b7ylfvm.fsf@bzzz.home.net> (raw)
In-Reply-To: <E1GXeYv-0006rP-RV@candygram.thunk.org> (Theodore Ts'o's message of "Wed\, 11 Oct 2006 09\:55\:57 -0400")
>>>>> Theodore Ts'o (TT) writes:
TT> Storing the tail as an extended attribute
TT> =========================================
TT> BSD FFS/UFS Fragments
TT> =====================
what if we would apply BSD FFS/UFS Fragments design to inodes?
something like basic inode size is still 128 bytes, but we
could unite few contiguous inodes to a larger one and use that
space to store extented attributes, including a tail ?
I foresee couple issues:
a) as we can't predict tail size, we'd need to be able
to reallocate inode or do some sort of delayed inode
allocation
b) inode space is quite limited and this why we may exhaust
it very quickly
thanks, Alex
prev parent reply other threads:[~2006-12-02 11:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 13:55 Design alternatives for fragments/file tail support in ext4 Theodore Ts'o
2006-10-13 6:19 ` Michael Burschik
2006-10-13 8:10 ` Andreas Dilger
2006-10-13 10:49 ` Theodore Tso
2006-10-13 10:56 ` Alex Tomas
2006-10-13 12:23 ` Theodore Tso
2006-10-13 17:47 ` Andreas Dilger
2006-10-13 12:48 ` Erik Mouw
2006-12-02 11:02 ` Alex Tomas [this message]
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=m33b7ylfvm.fsf@bzzz.home.net \
--to=alex@clusterfs.com \
--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 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).