From: Mark Nelson <mark.nelson@inktank.com>
To: Tommi Virtanen <tv@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: TIER: combine SSDs and HDDs into a single block device
Date: Thu, 02 Aug 2012 12:02:44 -0500 [thread overview]
Message-ID: <501AB2B4.2010406@inktank.com> (raw)
In-Reply-To: <CADvuQRExAsO2yKo6pT+MMfj8Gwt7a7SGkkOgm-0kjQ+nRzU75g@mail.gmail.com>
On 8/2/12 11:13 AM, Tommi Virtanen wrote:
> Sounds like bcache in writeback mode. Assumes all underlying block
> devices are RAIDed, or losing one will mean losing data; that is, for
> example RAID1(SSD+SSD) & RAID5(8*HDD).
>
> http://www.lessfs.com/wordpress/?p=776
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Neat! I'll try to play with it once the test hardware all makes it in.
Alex is also trying to bug the XFS guys (and Sage bugged the BTRFS guys)
about ways to put metadata on SSD while keeping data on spinning disk.
It sounds like there is a hack for XFS that would let us keep inodes in
the lower portion of a volume up to some configurable boundary and then
we could use lvm to assign that portion of the volume to an SSD. The
BTRFS guys have a SOC project in the works to separate out metadata onto
another disk.
I think these kinds of things could really help our small request
performance.
Mark
next prev parent reply other threads:[~2012-08-02 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 16:13 TIER: combine SSDs and HDDs into a single block device Tommi Virtanen
2012-08-02 17:02 ` Mark Nelson [this message]
2012-08-02 17:19 ` Alex Elder
2012-08-02 17:57 ` Christoph Hellwig
2012-08-02 21:49 ` Mark Nelson
2012-08-03 7:22 ` Christoph Hellwig
2012-08-02 17:32 ` Calvin Morrow
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=501AB2B4.2010406@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=tv@inktank.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.