linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: daobang wang <wangdb1981@gmail.com>
Cc: "Mathias Burén" <mathias.buren@gmail.com>,
	linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID5 created by 8 disks works with xfs
Date: Sun, 01 Apr 2012 22:12:46 -0500	[thread overview]
Message-ID: <4F79192E.9020909@hardwarefreak.com> (raw)
In-Reply-To: <CACwgYDMXF9WEgzW9vL_0=GdRc_t+67WAkRTKNoKOMEMCvjujVw@mail.gmail.com>

On 4/1/2012 1:20 AM, daobang wang wrote:
> I have the different opinion, the application does not write the disk
> directly, disk IOs will be merged before writen in kernel, just we can
> not caculate how many IOs will be merged.

Your original workload description was writing 200 or 100 video streams
to 200 or 100 different files in parallel.  What you state above is
different than the original.  Maybe you could give us a little more
detail about how this application actually does its file IO.

-- 
Stan


  parent reply	other threads:[~2012-04-02  3:12 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-31  1:22 RAID5 created by 8 disks works with xfs daobang wang
2012-03-31  7:59 ` Mathias Burén
2012-03-31 20:09   ` Stan Hoeppner
2012-04-01  1:16     ` daobang wang
2012-04-01  2:05       ` daobang wang
2012-04-01  5:13         ` Stan Hoeppner
2012-04-01  3:51       ` Stan Hoeppner
2012-04-01  5:12         ` daobang wang
2012-04-01  5:40           ` Stan Hoeppner
2012-04-01  5:59             ` daobang wang
2012-04-01  6:20               ` daobang wang
2012-04-01  7:08                 ` Marcus Sorensen
2012-04-02  3:47                   ` Stan Hoeppner
2012-04-05  0:48                     ` daobang wang
     [not found]                       ` <CACwgYDOtCoVF-p+KKqPYxHhA4vWF78Ueecx9hcVWLoyxFWzV9Q@mail.gmail.com>
2012-04-05 21:01                         ` Stan Hoeppner
2012-04-06  0:25                           ` daobang wang
2012-04-06  2:33                             ` daobang wang
2012-04-06  6:00                               ` Jack Wang
2012-04-06  6:45                                 ` daobang wang
2012-04-06  6:49                                   ` daobang wang
2012-04-06  8:18                                     ` Stan Hoeppner
2012-04-06  8:45                                       ` daobang wang
2012-04-06 11:12                                         ` Stan Hoeppner
2012-04-18  2:23                                           ` daobang wang
2012-04-02  3:12                 ` Stan Hoeppner [this message]
2012-04-01 10:33             ` David Brown
2012-04-01 12:28               ` John Robinson
2012-04-02  6:59                 ` David Brown
     [not found]                 ` <CA+res+QkLi7sxZrD-XOcbR47CeJ5gADf7P6pa1w1oMf8CKSB4g@mail.gmail.com>
2012-04-02  8:01                   ` John Robinson
2012-04-02 10:01                     ` Jack Wang
2012-04-02 10:28                       ` John Robinson
2012-04-02 20:41                         ` Stan Hoeppner
2012-04-02  5:43               ` Stan Hoeppner
2012-04-02  7:04                 ` David Brown
2012-04-02 20:21                   ` Stan Hoeppner
2012-04-01  4:52       ` Stan Hoeppner
2012-04-01  8:06         ` John Robinson

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=4F79192E.9020909@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mathias.buren@gmail.com \
    --cc=wangdb1981@gmail.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).