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 February 2012
Date: Sun, 18 Mar 2012 04:26:19 -0400 [thread overview]
Message-ID: <20120318082619.GA28069@infradead.org> (raw)
February has been been busy with development for Linux 3.3, although only
little new code made it to the development tree yet, mostly a refactor
of the log grant code. Patch traffic on the mailing list included a rewrite
of disk quota caching, yielding dramatic performance improvements for systems
with lots of quotas, a series to make all inode updates and thus all live
metadata updates transactional. Last but not least a version versions to
fix a long standing bug in support of the real time subvolume was posted,
showing that even this long deprecated feature still has a user base.
On the userspace side development has been quite, with just two fixes to
xfs_io committed to xfsprogs, while waiting for the long overdue 3.1.8
release. Xfsdump has been entirely quite this month, again waiting for
a release, and xfstests saw only two commits either, although there are
still lots of outstanding patches on the list that haven't been reviewed
and/or applied.
reply other threads:[~2012-03-18 8:26 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=20120318082619.GA28069@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).