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 May 2012
Date: Mon, 18 Jun 2012 08:08:53 -0400 [thread overview]
Message-ID: <20120618120853.GA15480@infradead.org> (raw)
May saw the release of Linux 3.4, including a decent sized XFS update.
Remarkable XFS features in Linux 3.4 include moving over all metadata
updates to use transactions, the addition of a work queue for the
low-level allocator code to avoid stack overflows due to extreme stack
use in the Linux VM/VFS call chain, better xattr operation tracing,
fixes for a long-standing but hard to hit deadlock when using the XFS
real time subvolume, and big improvements in disk quota scalability.
The final diffstat for XFS in Linux 3.4 is:
61 files changed, 1692 insertions(+), 2356 deletions(-)
In the meantime the merge window for Linux 3.5 opened, and another large
update has been merged into Linus' tree. Interesting changes in Linux
3.5-rc1 include improved error handling on buffer write failures,
a drastic reduction of locking overhead when doing high-IOPS direct I/O,
removal of the old xfsbufd daemon in favor of writing most run-time
metadata from the xfsaild daemon, deferral of CIL pushes to decouple
user space metadata I/O from log writeback, and last but not least the
addition of the SEEK_DATA/SEEK_HOLE lseek arguments that allow user space
programs to deal with sparse files efficiently. Traffic on the mailing list
has been a bit quiet in May, mostly focusing on a wide range of bug fixes,
but little new features.
On the user space side xfs_repair saw a few bug fixes posted to the list
that didn't make it to the repository yet, while xfstests saw it's usual
amount of minor bug fixes.
next reply other threads:[~2012-06-18 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 12:08 Christoph Hellwig [this message]
2012-06-18 18:25 ` XFS status update for May 2012 Andreas Dilger
2012-06-18 18:43 ` Ben Myers
2012-06-18 20:36 ` Andreas Dilger
2012-06-19 1:20 ` Dave Chinner
2012-06-18 21:11 ` Eric Sandeen
2012-06-18 21:16 ` Eric Sandeen
2012-06-19 1:27 ` Dave Chinner
2012-06-19 1:11 ` Dave Chinner
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=20120618120853.GA15480@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).