All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Michael Evans <mjevans1983@gmail.com>
Cc: Chris Worley <worleys@gmail.com>, Sujit K M <sjt.kar@gmail.com>,
	linuxraid <linux-raid@vger.kernel.org>
Subject: Re: Unbelievably _good_ write performance: RHEL5.4 mirror
Date: Wed, 04 Nov 2009 15:40:47 +0300	[thread overview]
Message-ID: <4AF1764F.20302@msgid.tls.msk.ru> (raw)
In-Reply-To: <4877c76c0911031629n580dc25ay7e47990908b056e7@mail.gmail.com>

Michael Evans wrote:
>> So, you're saying that the MD layer is doing it's own buffering?  Are
>> you sure?  With the system cache disabled and the drive (and block
>> device driver) cache disabled, there should be no reason to require
>> synchronous I/O, unless, as you suggest, the MD layer is broken.
>>
>> You're saying that both O_DIRECT and O_SYNC must be used to disable
>> cache effects. Why then are there two separate flags and not just one?
>>  Synchronous is a very different behavior that is not necessary for
>> this test and put additional requirements that are not needed for this
>> test.
>>
>> Chris
>>
> 
> Reading the manual page it seems O_DIRECT explicitly minimizes any
> attempts at extra copying; not explicitly disabling buffers, merely
> not adding more.  In another mail thread this tweak-able was
> discussed:
> 
> echo 0 > /sys/block/md*/md/stripe_cache_size

stripe_cache_size only exists for raid4, raid5 and raid6.
It never existed for other raid levels because it's pointless.

/mjt

      parent reply	other threads:[~2009-11-04 12:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 18:28 Unbelievably _good_ write performance: RHEL5.4 mirror Chris Worley
2009-11-03 12:37 ` Sujit K M
2009-11-03 16:31   ` Michael Evans
2009-11-03 19:29     ` Chris Worley
2009-11-04  0:11       ` Michael Evans
2009-11-04  0:21         ` Chris Worley
2009-11-04  0:29           ` Michael Evans
2009-11-04  0:37             ` Chris Worley
2009-11-04  0:41               ` Michael Evans
2009-11-04  3:45                 ` NeilBrown
2009-11-04 12:40             ` Michael Tokarev [this message]

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=4AF1764F.20302@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=linux-raid@vger.kernel.org \
    --cc=mjevans1983@gmail.com \
    --cc=sjt.kar@gmail.com \
    --cc=worleys@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.