From: Radek Pazdera <rpazdera@redhat.com>
To: linux-ext4@vger.kernel.org
Cc: lczerner@redhat.com, kasparek@fit.vutbr.cz,
Radek Pazdera <rpazdera@redhat.com>
Subject: [PATCH v2 2/2] mke2fs, tune2fs: Adding support for the itree flag
Date: Mon, 13 May 2013 17:43:50 +0200 [thread overview]
Message-ID: <1368459830-3651-3-git-send-email-rpazdera@redhat.com> (raw)
In-Reply-To: <1368459830-3651-1-git-send-email-rpazdera@redhat.com>
This commit enables the itree feature flag for the mke2fs and tune2fs.
The 'itree' feature adds an auxiliary tree that should help with indexing
directories. The tree resides on the file system along with the original
HTree (althought it is placed outside of the directory file).
It is a B+tree that contains directory entries sorted in inode order and
it is used to implement the getdents/readdir system calls. The inodes
are then returned in the optimal order, which improves the performance of
directory traversal.
Signed-off-by: Radek Pazdera <rpazdera@redhat.com>
---
misc/mke2fs.c | 3 ++-
misc/tune2fs.c | 6 ++++--
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/misc/mke2fs.c b/misc/mke2fs.c
index 7ff759d..672bcde 100644
--- a/misc/mke2fs.c
+++ b/misc/mke2fs.c
@@ -914,7 +914,8 @@ static __u32 ok_features[3] = {
#ifdef CONFIG_QUOTA
EXT4_FEATURE_RO_COMPAT_QUOTA|
#endif
- EXT4_FEATURE_RO_COMPAT_METADATA_CSUM
+ EXT4_FEATURE_RO_COMPAT_METADATA_CSUM|
+ EXT4_FEATURE_RO_COMPAT_ITREE
};
diff --git a/misc/tune2fs.c b/misc/tune2fs.c
index 332aafd..a638d55 100644
--- a/misc/tune2fs.c
+++ b/misc/tune2fs.c
@@ -148,7 +148,8 @@ static __u32 ok_features[3] = {
#ifdef CONFIG_QUOTA
EXT4_FEATURE_RO_COMPAT_QUOTA |
#endif
- EXT4_FEATURE_RO_COMPAT_METADATA_CSUM
+ EXT4_FEATURE_RO_COMPAT_METADATA_CSUM|
+ EXT4_FEATURE_RO_COMPAT_ITREE
};
static __u32 clear_ok_features[3] = {
@@ -169,7 +170,8 @@ static __u32 clear_ok_features[3] = {
#ifdef CONFIG_QUOTA
EXT4_FEATURE_RO_COMPAT_QUOTA |
#endif
- EXT4_FEATURE_RO_COMPAT_METADATA_CSUM
+ EXT4_FEATURE_RO_COMPAT_METADATA_CSUM|
+ EXT4_FEATURE_RO_COMPAT_ITREE
};
/*
--
1.7.7.6
prev parent reply other threads:[~2013-05-13 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 15:43 [PATCH v2 0/2] e2fsprogs: Adding itree feature/inode flags Radek Pazdera
2013-05-13 15:43 ` [PATCH v2 1/2] libext2fs: Adding itree feature and inode flags Radek Pazdera
2013-05-13 15:43 ` Radek Pazdera [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=1368459830-3651-3-git-send-email-rpazdera@redhat.com \
--to=rpazdera@redhat.com \
--cc=kasparek@fit.vutbr.cz \
--cc=lczerner@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).