From: Christoph Hellwig <hch@infradead.org>
To: Roel van Meer <rolek@bokxing.nl>
Cc: xfs@oss.sgi.com
Subject: Re: XFS status update for May 2010
Date: Wed, 16 Jun 2010 05:42:00 -0400 [thread overview]
Message-ID: <20100616094200.GB16216@infradead.org> (raw)
In-Reply-To: <cone.1276679587.153934.32947.1001@bork.lsof.org>
On Wed, Jun 16, 2010 at 11:13:07AM +0200, Roel van Meer wrote:
> 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.
As long as things just work everything is perfect! If you have any
performance numbers that compare to older kernel / the non delayed
logging case for your workload we would certainly be interested in them.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-06-16 9:39 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
2010-06-16 9:42 ` Christoph Hellwig [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=20100616094200.GB16216@infradead.org \
--to=hch@infradead.org \
--cc=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