From: Neil Brown <neilb@suse.de>
To: David Rees <drees76@gmail.com>
Cc: Bill Davidsen <davidsen@tmr.com>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Thoughts on using SSD
Date: Fri, 27 Mar 2009 15:31:37 +1100 [thread overview]
Message-ID: <18892.22185.768994.295766@notabene.brown> (raw)
In-Reply-To: message from David Rees on Thursday March 26
On Thursday March 26, drees76@gmail.com wrote:
> On Thu, Mar 26, 2009 at 4:09 PM, Bill Davidsen <davidsen@tmr.com> wrote:
> > If I were to create a small raid device, raid1, made of the 4GB Ssd and 4GB
> > of SATA space, if I made the SATA write-mostly and write-behind, and put the
> > journal for my raid arrays (and bitmaps?) that seems likely to provide a
> > significant performance gain in small storage.
> >
> > Am I missing anything here? Is there an obvious drawback I'm missing?
>
> Yeah, the fact that it doesn't seem to be possible to take advantage
> of the write-behind feature? :-p
>
> Besides fsync, I think it may have something to do with barriers. As
> in, when you flush a barrier, that causes entire cache to get flushed
> to disk, including your write-behind disk.
Nope. The barriers are sent separately to both devices. Yes, they
both get flushed, but we don't wait for the write-behind flush to
complete.
NeilBrown
>
> Hopefully Neil can chime in here. I found this thread from a while
> back which seemed relevant, but I haven't been able to digest the
> whole thing yet: http://lkml.org/lkml/2007/5/25/71
>
> -Dave
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-27 4:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 23:09 Thoughts on using SSD Bill Davidsen
2009-03-27 0:51 ` David Rees
2009-03-27 4:31 ` Neil Brown [this message]
2009-03-27 4:37 ` Neil Brown
2009-04-03 23:28 ` Lars Marowsky-Bree
2009-04-09 22:26 ` Bill Davidsen
2009-04-10 9:14 ` Neil Brown
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=18892.22185.768994.295766@notabene.brown \
--to=neilb@suse.de \
--cc=davidsen@tmr.com \
--cc=drees76@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 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).