From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: XFS status update for April 2012
Date: Tue, 8 May 2012 11:35:51 -0400 [thread overview]
Message-ID: <20120508153551.GB8176@infradead.org> (raw)
April was a relatively quite month in XFS development, partially because
most XFS developers traveled to San Francisco for the Linux Filesystem
and Storage Summit and the first XFS developers meeting co hosted at the
Linux Foundation Collaboration Summit.
The XFS development tree only saw a series to reduce ilock hold times and
a few patches merged. Traffic on the mailing list list has been a bit more
busy, with a few patchset being reposted again and again after various
updates. Features still scheduled for Linux 3.5 include: removal of
the xfsbufd daemon, various other cleanups of the buffer layer, moving
CIL commits into a background thread and thus reducing the impact on
threads causing the commits, as well as a bigger than usual set of
cleanups and fixes.
The user space side as been extremely slow with no patches applied and
very few posted to the mailing list.
reply other threads:[~2012-05-08 15:35 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=20120508153551.GB8176@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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).