public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: ext4 roadmap
Date: Wed, 01 Nov 2006 17:16:37 -0600	[thread overview]
Message-ID: <1162422997.13777.35.camel@kleikamp.austin.ibm.com> (raw)

It has been discussed in the conference call that we need to better
define the requirements for ext4 and set some kind of target for when
new function should be added, so we can then work on stabilizing the
code and getting it production-ready.  The list below is based on the
candidate features list in Documentation/filesystems/ext4.txt.  It is by
no means complete, as some other ideas are being floated around, and I
very well may have missed some features.

I plan to put this in a wiki, but I'm not sure what the best place is.
Neither http://fedoraproject.org/wiki/ext3-devel nor
https://mail.clusterfs.com/wikis/lustre/Ext3Development has been kept up
to date, but I'd be happy to use either.

Here's something to start with:

Multiblock Allocation
---------------------
Primary developer: Alex Tomas
Status:	Patches available
Changes on-disk format: No
Target Date: ?
e2fsprogs changes: No

Delayed Allocation
------------------
Primary developer: Alex Tomas
Status:	Patches available
Changes on-disk format: No
Target Date: ?
e2fsprogs changes: No

Break 32000 subdirectory limit
------------------------------
Primary developer: Andreas? Ted?
Status:	Patches available
Changes on-disk format: Yes
Target Date: ?
e2fsprogs changes: Needed

nsec timestamps
---------------
Primary developer: Andreas? Alex?
Status: Patches available
Change on-disk format: Yes
Target Date: ?
e2fsprogs changes: Needed

inode version on disk
---------------------
Primary developer: ?
Status: Prototype available
Change on-disk format: Yes
Target Date: ?
e2fsprogs changes: Needed

uninitialized groups
--------------------
Primary developer: ?
Status: Prototype available
Change on-disk format: Yes
Target Date: ?
e2fsprogs changes: Needed

journal checksumming
--------------------
Primary developer: Andreas?
Status: Prototype available
Change on-disk format: Yes
Target Date: ?
e2fsprogs changes: Needed

persistent preallocation
------------------------
Primary developer: Suparna?
Status: In development
Change on-disk format: Yes
Target Date: ?
e2fsprogs changes: Needed

-- 
David Kleikamp
IBM Linux Technology Center

             reply	other threads:[~2006-11-01 23:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01 23:16 Dave Kleikamp [this message]
2006-11-01 23:52 ` ext4 roadmap Grzegorz Kulewski
2006-11-02  1:17   ` Andreas Dilger
2006-11-02  1:44     ` Grzegorz Kulewski

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=1162422997.13777.35.camel@kleikamp.austin.ibm.com \
    --to=shaggy@austin.ibm.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