From: dcg <diegocg@gmail.com>
To: linux-ext4@vger.kernel.org, tytso@mit.edu
Subject: [PATCH] Update Documentation/filesystems/ext4.txt
Date: Fri, 17 Oct 2008 01:10:08 +0200 [thread overview]
Message-ID: <20081017011008.6c3b12ef@diego-desktop> (raw)
Since Ext4 is supposed to be stable in 2.6.28-rc, Documentation should be
updated...it needs more updates, of course, I don't really know what
parts should really be updated
PD: the wiki needs some update aswell.
Signed-off-by: Diego Calleja <diegocg@gmail.com>
Index: 2.6/Documentation/filesystems/ext4.txt
===================================================================
--- 2.6.orig/Documentation/filesystems/ext4.txt 2008-10-17 01:01:50.000000000 +0200
+++ 2.6/Documentation/filesystems/ext4.txt 2008-10-17 01:04:38.000000000 +0200
@@ -2,10 +2,10 @@
Ext4 Filesystem
===============
-This is a development version of the ext4 filesystem, an advanced level
-of the ext3 filesystem which incorporates scalability and reliability
-enhancements for supporting large filesystems (64 bit) in keeping with
-increasing disk capacities and state-of-the-art feature requirements.
+Ext4 is an an advanced level of the ext3 filesystem which incorporates
+scalability and reliability enhancements for supporting large filesystems
+(64 bit) in keeping with increasing disk capacities and state-of-the-art
+feature requirements.
Mailing list: linux-ext4@vger.kernel.org
@@ -40,7 +40,7 @@
the test_fs flag to indicate that it's ok for an in-development
filesystem to touch this filesystem:
- # tune2fs -O extents -E test_fs /dev/hda1
+ # tune2fs -O extents /dev/hda1
If the filesystem was created with 128 byte inodes, it can be
converted to use 256 byte for greater efficiency via:
@@ -68,7 +68,7 @@
2.1 Currently available
-* ability to use filesystems > 16TB (e2fsprogs support not available yet)
+* ability to use filesystems > 16TB
* extent format reduces metadata overhead (RAM, IO for access, transactions)
* extent format more robust in face of on-disk corruption due to magics,
* internal redunancy in tree
@@ -101,12 +101,6 @@
metadata checksumming have been discussed and planned for a bit but no patches
exist yet so I'm not sure they're in the near-term roadmap.
-The big performance win will come with mballoc, delalloc and flex_bg
-grouping of bitmaps and inode tables. Some test results available here:
-
- - http://www.bullopensource.org/ext4/20080530/ffsb-write-2.6.26-rc2.html
- - http://www.bullopensource.org/ext4/20080530/ffsb-readwrite-2.6.26-rc2.html
next reply other threads:[~2008-10-16 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 23:10 dcg [this message]
2008-10-17 11:11 ` [PATCH] Update Documentation/filesystems/ext4.txt Theodore Tso
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=20081017011008.6c3b12ef@diego-desktop \
--to=diegocg@gmail.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