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 January 2011
Date: Sun, 13 Feb 2011 13:42:19 -0500 [thread overview]
Message-ID: <20110213184219.GA22792@infradead.org> (raw)
On the 4th of January we saw the release of Linux 2.6.37, which contains a
large XFS update:
67 files changed, 1424 insertions(+), 1524 deletions(-)
User visible changes are the new XFS_IOC_ZERO_RANGE ioctl which allows
to convert already allocated space into unwritten extents that return
zeros on a read, and support for 32-bit wide project IDs. The other large
item are various changes to improve metadata scalability even further,
by changes to the the buffer cache, inode lookup and other parts of the
filesystem driver.
After that the XFS development tree for 2.6.38 was merged into mainline,
with an even larger set of changes. Notable items include support for the
FITRIM ioctl to discard unused space on SSDs and thinly provisioned storage
systems, a buffer LRU scheme to improve hit rates for metadata, an
overhaul of the log subsystem locking, dramatically improving scalability
in that area, and much smarter handling of preallocations, especially
for files closed and reopened frequently, e.g. by the NFS server.
User space development has been very quite, with just a few fixes committed
to the xfstests repository, although various additional patches for xfsprogs
and xfstests that haven't been committed yet were discussed on the mailing list.
WARNING: multiple messages have this Message-ID (diff)
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 January 2011
Date: Sun, 13 Feb 2011 13:42:19 -0500 [thread overview]
Message-ID: <20110213184219.GA22792@infradead.org> (raw)
On the 4th of January we saw the release of Linux 2.6.37, which contains a
large XFS update:
67 files changed, 1424 insertions(+), 1524 deletions(-)
User visible changes are the new XFS_IOC_ZERO_RANGE ioctl which allows
to convert already allocated space into unwritten extents that return
zeros on a read, and support for 32-bit wide project IDs. The other large
item are various changes to improve metadata scalability even further,
by changes to the the buffer cache, inode lookup and other parts of the
filesystem driver.
After that the XFS development tree for 2.6.38 was merged into mainline,
with an even larger set of changes. Notable items include support for the
FITRIM ioctl to discard unused space on SSDs and thinly provisioned storage
systems, a buffer LRU scheme to improve hit rates for metadata, an
overhaul of the log subsystem locking, dramatically improving scalability
in that area, and much smarter handling of preallocations, especially
for files closed and reopened frequently, e.g. by the NFS server.
User space development has been very quite, with just a few fixes committed
to the xfstests repository, although various additional patches for xfsprogs
and xfstests that haven't been committed yet were discussed on the mailing list.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-02-13 18:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 18:42 Christoph Hellwig [this message]
2011-02-13 18:42 ` XFS status update for January 2011 Christoph Hellwig
2011-02-14 2:17 ` Tao Ma
2011-02-14 2:17 ` Tao Ma
2011-02-14 12:02 ` Dave Chinner
2011-02-14 12:02 ` Dave Chinner
2011-02-14 15:20 ` tm
2011-02-14 15:20 ` tm
2011-02-14 23:55 ` Dave Chinner
2011-02-14 23:55 ` Dave Chinner
2011-02-15 2:01 ` Tao Ma
2011-02-15 2:01 ` Tao Ma
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=20110213184219.GA22792@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.