From: Mark Nelson <mark.nelson@inktank.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Tommi Virtanen <tv@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: TIER: combine SSDs and HDDs into a single block device
Date: Thu, 02 Aug 2012 16:49:11 -0500 [thread overview]
Message-ID: <501AF5D7.9060004@inktank.com> (raw)
In-Reply-To: <20120802175700.GA16693@infradead.org>
On 08/02/2012 12:57 PM, Christoph Hellwig wrote:
> On Thu, Aug 02, 2012 at 12:02:44PM -0500, Mark Nelson wrote:
>> 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.
>
> Also with XFS you can use the realtime device for data and the main
> device for all metadata.
>
I was thinking of doing that. Is the realtime allocator a good fit for
this kind of thing? I think dchinner mentioned on the xfs mailing list
last year that it's single threaded and not very well optimized (and
maybe not production viable?)
Mark
--
Mark Nelson
Performance Engineer
Inktank
next prev parent reply other threads:[~2012-08-02 21:49 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
2012-08-02 17:19 ` Alex Elder
2012-08-02 17:57 ` Christoph Hellwig
2012-08-02 21:49 ` Mark Nelson [this message]
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=501AF5D7.9060004@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=hch@infradead.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.