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 July 2012
Date: Mon, 13 Aug 2012 05:15:17 -0400 [thread overview]
Message-ID: <20120813091517.GA27609@infradead.org> (raw)
July saw the release of Linux 3.5, which included an average sized XFS
update:
81 files changed, 2633 insertions(+), 3004 deletions(-)
Noteworthy updates in Linux 3.5 include the removal of the xfsbufd
background thread which writes metadata buffers, background processing
of CIL flushes and thus lower average latency for metadata heavy
workloads, as well a a reduction of lock hold times and frequency during
reads and writes. The large XFS update for the Linux 3.6 merge window
did not get merged yet by the end of July, but will bring better support
for large directory block sizes, a faster inode allocator and a large
amount of bug fixes in different areas of the code. Development on the list
has been fairly busy on the patchsets to support group and project quotas
at the same time, as well as improved SEEK_HOLE/SEEK_DATA support but
otherwise mostly limited to bug fixes and smaller cleanups.
Userpace development has been rather slow with a single fix for xfs_db
and another single fix in xfstests.
reply other threads:[~2012-08-13 9:15 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=20120813091517.GA27609@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).