From: Roel van Meer <rolek@bokxing.nl>
To: xfs@oss.sgi.com
Subject: Re: XFS status update for May 2010
Date: Wed, 16 Jun 2010 11:13:07 +0200 [thread overview]
Message-ID: <cone.1276679587.153934.32947.1001@bork.lsof.org> (raw)
In-Reply-To: 20100615132221.GA17385@infradead.org
Christoph Hellwig writes:
> Meanwhile active development aimed at 2.6.35 merge progressed. The
> major feature for this window is the merge of the delayed logging code,
> which adds a new logging mode that dramatically reduces the bandwidth
> required for log I/O. See the documentation [1] for details. Testers
> for this new code are welcome.
As of today I'm running 2.6.35-rc3 with XFS and delayed logging on a 4GB
software raid0 we use to do nightly builds of about 150 software packages
(kernel, samba, etc) on Slackware 10.1.
If there's anything specific I can do, please let me know. I have some more
hardware around to test with.
By the way: thanks for these monthly status updates: they're really useful!
Regards,
roel
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-06-16 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 13:22 XFS status update for May 2010 Christoph Hellwig
2010-06-16 9:13 ` Roel van Meer [this message]
2010-06-16 9:42 ` Christoph Hellwig
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=cone.1276679587.153934.32947.1001@bork.lsof.org \
--to=rolek@bokxing.nl \
--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