From: Eric Sandeen <sandeen@sandeen.net>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: [Fwd: Benchmarking data from a raid machine 2.6.34-rc3]
Date: Sat, 24 Apr 2010 09:32:57 -0500 [thread overview]
Message-ID: <4BD30119.3020404@sandeen.net> (raw)
In-Reply-To: <4BD27923.1020208@hardwarefreak.com>
Stan Hoeppner wrote:
> Eric Sandeen put forth on 4/23/2010 9:46 PM:
>> FYI...
>>
>> I asked Keith if he could do xfs nobarrier runs as well.
>>
>> If there are ext4 nobarrier runs "winning" it seems only fair. :)
>
> Do you have a link to the hardware specs used in the testing Eric?
>
> Thanks.
>
There are machine specs at http://btrfs.boxacle.net/ but I don't know
for -sure- that he's testing the exact same setup now.
I assume so, though. (I shoulda included that top URL in the message)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-04-24 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 2:46 [Fwd: Benchmarking data from a raid machine 2.6.34-rc3] Eric Sandeen
2010-04-24 4:52 ` Stan Hoeppner
2010-04-24 14:32 ` Eric Sandeen [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=4BD30119.3020404@sandeen.net \
--to=sandeen@sandeen.net \
--cc=stan@hardwarefreak.com \
--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