All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "Majed B." <majedb@gmail.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Write-intent bitmap decreases or increase performance of RAID5?
Date: Sun, 04 Jul 2010 20:14:21 -0400	[thread overview]
Message-ID: <4C3123DD.9090509@tmr.com> (raw)
In-Reply-To: <AANLkTilnBWCGHUgQnmrzSzpo7TRYSedBVUZEOHKI4MmG@mail.gmail.com>

Majed B. wrote:
> How much RAM does your machine have?
>
> Write to the disk an amount that is larger than the amount of RAM and
> see if you get the same result.
>
> Also you can use hdparm to flush the caches before running dd the 2nd time.
>   

See the meaning of the fdatasync option to dd and the 
/proc/sys/vm/drop_cache control. You are right about hdparm, but it only 
matters if you are using tiny data, drive caches are small.

-- 
Bill Davidsen <davidsen@tmr.com>
  "We can't solve today's problems by using the same thinking we
   used in creating them." - Einstein


  parent reply	other threads:[~2010-07-05  0:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 20:11 Write-intent bitmap decreases or increase performance of RAID5? Shaochun Wang
2010-06-30  5:18 ` Roman Mamedov
2010-06-30  5:54   ` Mikael Abrahamsson
2010-06-30  5:59     ` Roman Mamedov
2010-06-30  6:58       ` Mikael Abrahamsson
2010-06-30  8:23         ` Roman Mamedov
2010-06-30 18:31           ` CoolCold
2010-07-05  0:11         ` Bill Davidsen
2010-07-01  6:40     ` Shaochun Wang
2010-07-01 20:30       ` Majed B.
2010-07-01 20:50         ` Roman Mamedov
2010-07-05  0:14         ` Bill Davidsen [this message]
2010-07-01 20:49       ` Roman Mamedov
2010-07-02 11:13         ` John Robinson
2010-07-05  0:17         ` 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=4C3123DD.9090509@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=majedb@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 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.