From: Alex Elsayed <eternaleye@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: RAID device nomination (Feature request)
Date: Thu, 18 Apr 2013 20:05:58 -0700 [thread overview]
Message-ID: <kkqcaj$9o2$1@ger.gmane.org> (raw)
In-Reply-To: kkq3qu$t2q$1@ger.gmane.org
Martin wrote:
<snip>
> Or perhaps include the same Ceph code routines into btrfs?...
That's actually what I was thinking. The CRUSH code is actually already
pretty well factored out - it lives in net/ceph/crush/ in the kernel source
tree, and is treated as part of 'libceph' (which is used by both the Ceph
filesystem in fs/ceph/ and the RBD block device in drivers/block/rbd.c).
prev parent reply other threads:[~2013-04-19 3:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 13:45 RAID device nomination (Feature request) Martin
2013-04-18 14:06 ` Hugo Mills
2013-04-18 16:29 ` Martin
2013-04-18 19:44 ` Hugo Mills
2013-04-19 0:31 ` Martin
2013-04-18 19:48 ` Alex Elsayed
2013-04-19 0:41 ` Martin
2013-04-19 3:05 ` Alex Elsayed [this message]
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='kkqcaj$9o2$1@ger.gmane.org' \
--to=eternaleye@gmail.com \
--cc=linux-btrfs@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 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.