linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Dave Chinner <david@fromorbit.com>,
	linux-raid@vger.kernel.org,
	Justin Piszcz <jpiszcz@lucidpixels.com>,
	xfs@oss.sgi.com
Subject: Re: Optimize RAID0 for max IOPS?
Date: Tue, 25 Jan 2011 13:51:23 +0100	[thread overview]
Message-ID: <20110125135123.0342f116@harpe.intellique.com> (raw)
In-Reply-To: <20110125124509.D76D6BB0B9@gemini.denx.de>

Le Tue, 25 Jan 2011 13:45:09 +0100
Wolfgang Denk <wd@denx.de> écrivait:

> > This is smelling like a case of barrier IOs on software raid on
> > cheap storage....  
> 
> Right. [Any way to avoid these, btw?] 

Easy enough, use the "nobarrier" mount option. 

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-01-25 12:51 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-18 21:01 Optimize RAID0 for max IOPS? Wolfgang Denk
2011-01-18 22:18 ` Roberto Spadim
2011-01-19  7:04   ` Wolfgang Denk
2011-01-18 23:15 ` Stefan /*St0fF*/ Hübner
2011-01-19  0:05   ` Roberto Spadim
2011-01-19  7:11     ` Wolfgang Denk
2011-01-19  8:18       ` Stefan /*St0fF*/ Hübner
2011-01-19  8:29         ` Jaap Crezee
2011-01-19  9:32           ` Jan Kasprzak
2011-01-19  7:10   ` Wolfgang Denk
2011-01-19 19:21   ` Wolfgang Denk
2011-01-19 19:50     ` Roberto Spadim
2011-01-19 22:36       ` Stefan /*St0fF*/ Hübner
2011-01-19 23:09         ` Roberto Spadim
2011-01-19 23:18           ` Roberto Spadim
2011-01-20  2:48             ` Keld Jørn Simonsen
2011-01-20  3:53               ` Roberto Spadim
2011-01-21 19:34             ` Wolfgang Denk
2011-01-21 20:03               ` Roberto Spadim
2011-01-21 20:04                 ` Roberto Spadim
2011-01-24 14:40     ` CoolCold
2011-01-24 15:25       ` Justin Piszcz
2011-01-24 20:48         ` Wolfgang Denk
2011-01-24 21:57         ` Wolfgang Denk
2011-01-24 23:03           ` Dave Chinner
2011-01-25  7:39             ` Emmanuel Florac
2011-01-25  8:36               ` Dave Chinner
2011-01-25 12:45                 ` Wolfgang Denk
2011-01-25 12:51                   ` Emmanuel Florac [this message]
2011-01-24 20:43       ` Wolfgang Denk
2011-01-25 17:10 ` Christoph Hellwig
2011-01-25 18:41   ` Wolfgang Denk
2011-01-25 21:35     ` Christoph Hellwig
2011-01-26  7:16       ` Wolfgang Denk
2011-01-26  8:32         ` Stan Hoeppner
2011-01-26  8:42           ` Wolfgang Denk
2011-01-26  9:38         ` Christoph Hellwig
2011-01-26  9:41           ` CoolCold

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=20110125135123.0342f116@harpe.intellique.com \
    --to=eflorac@intellique.com \
    --cc=david@fromorbit.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=wd@denx.de \
    --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;
as well as URLs for NNTP newsgroup(s).