All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: Learner Study <learner.study@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Linux Raid performance
Date: Sun, 4 Apr 2010 11:46:48 -0700	[thread overview]
Message-ID: <k2t5bdc1c8b1004041146uec5162b8x5c95bfda2153ebd@mail.gmail.com> (raw)
In-Reply-To: <w2j7efa8a7d1004041126id2b84d47k7bd275606712d0e3@mail.gmail.com>

On Sun, Apr 4, 2010 at 11:26 AM, Learner Study <learner.study@gmail.com> wrote:
> Happy Easter!!!
>
> So, 550-600MB/s is the best we have seen with Linux raid using 16-24 SAS drives.
>
> Not sure if its appropriate to ask on this list - has someone seen
> better numbers with non-linux raid stack? Perhaps freebsd/lustre..
>
> Thanks for your time!
>

Are you just trolling or something? Why are you asking about non-linux
RAID on a Linux software RAID list?

I cannot believe the name Learner Study is real, is it? Possibly it
would make sense to first study, and from that hopefully learn, and
then come ask some questions with some depth to them?

- Mark

  reply	other threads:[~2010-04-04 18:46 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31 19:42 Linux Raid performance Learner Study
2010-03-31 20:15 ` Keld Simonsen
2010-04-02  3:07   ` Learner Study
2010-04-02  9:58     ` Nicolae Mihalache
2010-04-02 17:58       ` Learner Study
2010-04-02 11:05     ` Keld Simonsen
2010-04-02 11:18       ` Keld Simonsen
2010-04-02 17:55       ` Learner Study
2010-04-02 21:14         ` Keld Simonsen
2010-04-02 21:37           ` Learner Study
2010-04-03 11:20             ` Keld Simonsen
2010-04-03 15:56               ` Learner Study
2010-04-04  1:58                 ` Keld Simonsen
2010-04-03  0:10           ` Learner Study
2010-04-03  0:39         ` Mark Knecht
2010-04-03  1:00           ` John Robinson
2010-04-03  1:14           ` Richard Scobie
2010-04-03  1:32             ` Mark Knecht
2010-04-03  1:37               ` Richard Scobie
2010-04-03  3:06                 ` Learner Study
2010-04-03  3:00             ` Learner Study
2010-04-03 19:27               ` Richard Scobie
2010-04-03 18:14             ` MRK
2010-04-03 19:56               ` Richard Scobie
2010-04-04 15:00                 ` MRK
2010-04-04 18:26                   ` Learner Study
2010-04-04 18:46                     ` Mark Knecht [this message]
2010-04-04 21:28                       ` Jools Wills
2010-04-04 22:38                         ` Mark Knecht
2010-04-05 10:07                           ` Learner Study
2010-04-05 16:35                             ` John Robinson
2010-04-04 22:24                       ` Guy Watkins
2010-04-05 13:49                         ` Drew
2010-04-04 23:24                   ` Richard Scobie
2010-04-05 11:20                     ` MRK
2010-04-05 19:49                       ` Richard Scobie
2010-04-05 21:03                         ` Drew
2010-04-05 22:20                           ` Richard Scobie
2010-04-05 23:49                           ` Roger Heflin
2010-04-14 20:50             ` Bill Davidsen

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=k2t5bdc1c8b1004041146uec5162b8x5c95bfda2153ebd@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=learner.study@gmail.com \
    --cc=linux-raid@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.