public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: XFS status update for November 2010
Date: Wed, 22 Dec 2010 10:53:01 +1100	[thread overview]
Message-ID: <20101221235301.GD4907@dastard> (raw)
In-Reply-To: <4D109047.8050300@panasas.com>

On Tue, Dec 21, 2010 at 01:32:23PM +0200, Boaz Harrosh wrote:
> On 12/20/2010 08:00 PM, Christoph Hellwig wrote:
> >>From looking at the kernel git commits November looked like a pretty
> > slow month with just two hand full fixes going into the release candidates
> > for Linux 2.6.37, and none at all going into the development tree.
> > But in this case git statistics didn't tell the whole story - there
> > was a lot of activity on patches for the next merge window on the list.
> > The focus in November was still at metadata scalability, with various
> > patchsets that improves parallel creates and unlinks again, and also
> > improves 8-way dbench throughput by 30%.  In addition to that there
> > were patches to improve preallocation for NFS servers, to simplify
> > the writeback code, and to remove the XFS-internal percpu counters
> > for free space for the generic kernel percpu counters, which just needed
> > a small improvement.
> > 
> > On the user space side we saw the release of xfsprogs 3.1.4, which
> > contains various accumulated bug fixes and Debian packaging updates.
> > The xfsdump tree saw a large update to speed up restore by using
> > mmap for an internal database and remove the limitation of ~ 214
> > million directory entries per dump file.  The xfstests test suite
> > saw three new testcases and various fixes, including support for the
> > hfsplus filesystem.
> 
> Hi Christoph, happy holidays
> 
> I love these reports you do, thank you
> 
> I have one small request, could you please post them to
> linux-fsdevel as well. linux-kernel@vger.kernel.org is so crowded
> I keep missing them.

Boaz, you can set up a modification watch on this page:

http://xfs.org/index.php/XFS_Status_Updates

as Christoph posts the updates there as well.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

      reply	other threads:[~2010-12-21 23:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 18:00 XFS status update for November 2010 Christoph Hellwig
2010-12-21 11:32 ` Boaz Harrosh
2010-12-21 23:53   ` Dave Chinner [this message]

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=20101221235301.GD4907@dastard \
    --to=david@fromorbit.com \
    --cc=bharrosh@panasas.com \
    --cc=hch@infradead.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