From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: linux-raid@vger.kernel.org
Subject: Best option for SSD caching on a md raid array?
Date: Sun, 07 Feb 2016 22:14:08 -0700 [thread overview]
Message-ID: <1670804.QnHtKWfib8@nell> (raw)
Hi,
I'm planning on setting up a dual raid5 array for hosting vm's off LVM, I would
like to add an ssd cache to help with typical server system loads, and some
mixed read/write loads for game servers.
I'm wondering what the "best" route for me to go is. There's a few options
that I know of, like flashcache, dm-cache, and bcache. The question is which of
those is better suited to my use case?
Also wondering which ones people here use, and what they use it for.
Thanks!
--
Thomas Fjellstrom
thomas@fjellstrom.ca
next reply other threads:[~2016-02-08 5:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 5:14 Thomas Fjellstrom [this message]
2016-02-08 8:36 ` Best option for SSD caching on a md raid array? David Brown
2016-02-08 15:45 ` Jens-U. Mozdzen
2016-02-08 20:21 ` Thomas Fjellstrom
2016-02-08 9:38 ` Mateusz Korniak
2016-02-08 15:34 ` John Stoffel
2016-02-10 22:13 ` Pasi Kärkkäinen
2016-02-10 22:21 ` John Stoffel
2016-02-10 22:54 ` Pasi Kärkkäinen
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=1670804.QnHtKWfib8@nell \
--to=thomas@fjellstrom.ca \
--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