From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: XFS status update for June 2012
Date: Tue, 24 Jul 2012 09:40:59 -0400 [thread overview]
Message-ID: <20120724134059.GA25901@infradead.org> (raw)
June has been a pretty slow month for XFS in Linus tree, as June saw the
stabilization of the Linux 3.5 and thus only a handful of important XFS
fixes. Development of the tree destined for the next merge window has been
a bit more busy with the addition of discontinuous buffers that replace the
dabuf layer which has performance issues and isn't easy to deal with in the
upcoming metadata checksumming as well as a few smaller cleanups.
The list saw various other patches not applied yet, most notable a
refactoring and speedup of the inode allocator, and a heavily discussed
rewrite of the mount option parsing.
On the user space side a small number of fixes to the handling of fragmented
directories were applied to xfs_repair, and xfstests saw a fix for handling
different versions of xfsdump.
reply other threads:[~2012-07-24 13:40 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=20120724134059.GA25901@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).