From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Hot topics for the next release
Date: Wed, 06 Aug 2008 10:21:51 -0400 [thread overview]
Message-ID: <1218032511.15342.73.camel@think.oraclecorp.com> (raw)
Hello everyone,
Now that v0.16 is out the door, I'd like to get a thread going on topics
people are interested in tackling next. The top of my list looks like
this:
Improved allocator threading
Better in-memory free space indexing (Josef)
Better fsync performance (Chris)
Improved offline fsck
NFS Support
O_DIRECT support
But anything on the development timeline is fair game. I'm shooting for
a smaller number of changes this time around so a new release can be cut
before the kernel summit and plumber's conference in mid-September.
-chris
next reply other threads:[~2008-08-06 14:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 14:21 Chris Mason [this message]
2008-08-06 14:58 ` Hot topics for the next release David Woodhouse
2008-08-06 15:13 ` Chris Mason
2008-08-06 15:26 ` Toei Rei
2008-08-06 18:45 ` David Woodhouse
2008-08-06 15:42 ` jim owens
2008-08-06 16:36 ` Chris Mason
2008-08-06 20:36 ` jim owens
2008-08-06 20:43 ` Chris Mason
2008-08-06 20:49 ` Joe Peterson
2008-08-06 20:53 ` Chris Mason
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=1218032511.15342.73.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@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