From: Kalpak Shah <Kalpak.Shah@Sun.COM>
To: linux-ext4 <linux-ext4@vger.kernel.org>
Cc: TheodoreTso <tytso@mit.edu>, Mingming Cao <cmm@us.ibm.com>,
Andreas Dilger <adilger@Sun.COM>
Subject: [PATCH 0/2] Large EAs for ext4
Date: Tue, 18 Nov 2008 02:06:11 +0530 [thread overview]
Message-ID: <1226954171.3972.69.camel@localhost> (raw)
Hi,
These are the updated patches for adding large EA support to ext4.
Changes suggested by Mingming and Andreas for earlier patches have been
incorporated in this version.
Large EAs with values greater than half the filesystem blocksize are
stored in an external inode.
Patch 1/2 - EA inodes are not connected to any directory and hence
ext4_new_inode() cannot make a decision about where to allocate the EA
inode. So we add a new goal argument to ext4_new_inode() so that the EA
inode can be allocated close to the parent inode.
Patch 2/2 - Adds actual support for large EAs.
Thanks,
Kalpak
reply other threads:[~2008-11-17 20:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1226954171.3972.69.camel@localhost \
--to=kalpak.shah@sun.com \
--cc=adilger@Sun.COM \
--cc=cmm@us.ibm.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).