linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Dave Chinner <david@fromorbit.com>
Cc: NeilBrown <neilb@suse.de>, David Brown <david.brown@hesbynett.no>,
	Michael Tokarev <mjt@tls.msk.ru>,
	Miquel van Smoorenburg <mikevs@xs4all.net>,
	Linux RAID <linux-raid@vger.kernel.org>,
	LKML@dastard.hardwarefreak.com
Subject: Re: O_DIRECT to md raid 6 is slow
Date: Mon, 20 Aug 2012 00:42:05 -0500	[thread overview]
Message-ID: <5031CE2D.8030600@hardwarefreak.com> (raw)
In-Reply-To: <20120820051951.GC19235@dastard>

On 8/20/2012 12:19 AM, Dave Chinner wrote:

> Oh, you're probably complaining about that write number.

I wasn't complaining.  You know me better than that.

The cops caught me robbing a bank.  Under pressure, I pointed at you and
said "He gave me the gun and ammo!". ;)  Of course it was completely my
responsibility for shooting myself in the foot with it. :)

> Either way, the point I was making in the original post stands -
> RAID6 sucks balls for most workloads as they only do small writes in
> comparison to the stripe width of the volume....

Agreed.  Which was the point I originally made in this thread.  "We"
simply got a minor detail wrong.  It seems folks on the linux-raid list
like to split every hair 2^6 times, with extremely valid points getting
lost when the discussion drops into the weeds.

Sorry I dragged you into this Dave.

-- 
Stan


  reply	other threads:[~2012-08-20  5:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15  0:49 O_DIRECT to md raid 6 is slow Andy Lutomirski
2012-08-15  1:07 ` kedacomkernel
2012-08-15  1:12   ` Andy Lutomirski
2012-08-15  1:23     ` kedacomkernel
2012-08-15 11:50 ` John Robinson
2012-08-15 17:57   ` Andy Lutomirski
2012-08-15 22:00     ` Stan Hoeppner
2012-08-15 22:10       ` Andy Lutomirski
2012-08-15 23:50         ` Stan Hoeppner
2012-08-16  1:08           ` Andy Lutomirski
2012-08-16  6:41           ` Roman Mamedov
     [not found]     ` <201208152307.q7FN7hMR008630@xs8.xs4all.nl>
     [not found]       ` <502CD3F8.70001@hardwarefreak.com>
     [not found]         ` <502D6B0A.6090508@xs4all.net>
     [not found]           ` <502DF357.8090205@hardwarefreak.com>
     [not found]             ` <502E2817.8040306@xs4all.net>
2012-08-18  5:09               ` Stan Hoeppner
2012-08-18 10:08                 ` Michael Tokarev
2012-08-19  3:17                   ` Stan Hoeppner
2012-08-19 14:01                     ` David Brown
2012-08-19 23:34                       ` Stan Hoeppner
2012-08-20  0:01                         ` NeilBrown
2012-08-20  4:44                           ` Stan Hoeppner
2012-08-20  5:19                             ` Dave Chinner
2012-08-20  5:42                               ` Stan Hoeppner [this message]
2012-08-20  7:47                           ` David Brown
2012-08-21 14:51                         ` Miquel van Smoorenburg
2012-08-22  3:59                           ` Stan Hoeppner
2012-08-19 17:02                     ` Chris Murphy

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=5031CE2D.8030600@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=LKML@dastard.hardwarefreak.com \
    --cc=david.brown@hesbynett.no \
    --cc=david@fromorbit.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mikevs@xs4all.net \
    --cc=mjt@tls.msk.ru \
    --cc=neilb@suse.de \
    /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).