From: NeilBrown <neilb@suse.de>
To: "Patrick J. LoPresti" <lopresti@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Two questions about stripe_cache_size
Date: Wed, 23 Feb 2011 09:24:22 +1100 [thread overview]
Message-ID: <20110223092422.230875fa@notabene.brown> (raw)
In-Reply-To: <AANLkTin-Ub0PAvdWDQwzqUyvzVDKia5FGGpyK4ip_=Lo@mail.gmail.com>
On Tue, 22 Feb 2011 14:13:14 -0800 "Patrick J. LoPresti" <lopresti@gmail.com>
wrote:
> Thanks, Neil. Actually, I think I have one more question... (Well,
> one question with many faces.)
>
> Is the stripe cache write-back, or write-through? If the latter, when
> does it get flushed to disk, exactly?
>
Write-through.
However I am tempted to make it write-back as filesystems now submit 'flush'
requests which can be used to flush the cache. I wonder if you would be able
to notice any performance difference...
NeilBrown
next prev parent reply other threads:[~2011-02-22 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 21:46 Two questions about stripe_cache_size Patrick J. LoPresti
2011-02-22 22:01 ` NeilBrown
2011-02-22 22:10 ` Roberto Spadim
2011-02-22 22:13 ` Patrick J. LoPresti
2011-02-22 22:24 ` NeilBrown [this message]
2011-02-22 22:26 ` Roberto Spadim
2011-02-22 22:35 ` Patrick J. LoPresti
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=20110223092422.230875fa@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lopresti@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