public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <ms@teamix.de>
To: Daniel Pocock <daniel@pocock.com.au>
Cc: Martin Steigerwald <Martin@lichtvoll.de>,
	Andreas Dilger <adilger@dilger.ca>,
	linux-ext4@vger.kernel.org
Subject: Re: ext4, barrier, md/RAID1 and write cache
Date: Wed, 9 May 2012 11:34:00 +0200	[thread overview]
Message-ID: <201205091134.00281.ms@teamix.de> (raw)
In-Reply-To: <201205090930.02731.ms@teamix.de>

Am Mittwoch, 9. Mai 2012 schrieb Martin Steigerwald:
> You could adapt to /usr/share/doc/fio/examples/iometer-file-access-server
> to  benchmark such a scenario. Also fsmark simulates such a heavy fsync()
> based quite well. I have packaged it for Debian, but its still in NEW
> queue. You can grab it from
> 
> http://people.teamix.net/~ms/debian/sid/
> 
> (32-Bit build, but easily buildable for amd64 as well)

I have uploaded 64-bit builds of both fsmark and newer fio 2.0.7 as I needed 
them for my own use. They are build for Wheezy/Sid, but according to 
dependencies should work on Squeeze as well.

-- 
Martin Steigerwald - teamix GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90

      reply	other threads:[~2012-05-09  9:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 10:47 ext4, barrier, md/RAID1 and write cache Daniel Pocock
2012-05-07 16:25 ` Martin Steigerwald
2012-05-07 16:44   ` Daniel Pocock
2012-05-07 16:54     ` Andreas Dilger
2012-05-07 17:28       ` Daniel Pocock
2012-05-07 18:59         ` Martin Steigerwald
2012-05-07 20:56           ` Daniel Pocock
2012-05-07 22:24             ` Martin Steigerwald
2012-05-07 23:23               ` Daniel Pocock
2012-05-08 14:55                 ` Martin Steigerwald
2012-05-08 15:28                   ` Daniel Pocock
2012-05-08 17:02                     ` Andreas Dilger
2012-05-09  7:30                     ` Martin Steigerwald
2012-05-09  9:34                       ` Martin Steigerwald [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=201205091134.00281.ms@teamix.de \
    --to=ms@teamix.de \
    --cc=Martin@lichtvoll.de \
    --cc=adilger@dilger.ca \
    --cc=daniel@pocock.com.au \
    --cc=linux-ext4@vger.kernel.org \
    /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