From: Lars Marowsky-Bree <lmb@suse.com>
To: ceph-devel@vger.kernel.org
Subject: Re: ceph-disk improvements
Date: Thu, 7 Apr 2016 11:26:27 +0200 [thread overview]
Message-ID: <20160407092627.GE26235@suse.de> (raw)
In-Reply-To: <2041558235.2113.160e133c-ee3f-4c6e-9b8b-e4d468651d78.open-xchange@ox.pcextreme.nl>
On 2016-04-02T07:54:05, Wido den Hollander <wido@42on.com> wrote:
>
> > Op 1 april 2016 om 17:36 schreef Sage Weil <sweil@redhat.com>:
> >
> >
> > Hi all,
> >
> > There are a couple of looming features for ceph-disk:
> >
> > 1- Support for additional devices when using BlueStore. There can be up
> > to three: the main device, a WAL/journal device (small, ~128MB, ideally
> > NVRAM), and a fast metadata device (as big as you have available; will be
> > used for internal metadata).
> >
> > 2- Support for setting up dm-cache, bcache, and/or FlashCache underneath
> > filestore or bluestore.
> >
>
> Keep in mind that you can't create a partition on a bcache device. So when using
> bcache, the journal has to be filebased and not a partition.
Is there a point to running the journal on bcache? I see a point for
bcache for the (potentially on HDD) actual data store - but the
WAL/journal, would that not be directly on NVMe/PM/SSD (at the very
least)? Without an intervening cache?
Regards,
Lars
--
Architect SDS, Distinguished Engineer
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
--
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
next prev parent reply other threads:[~2016-04-07 9:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 15:36 ceph-disk improvements Sage Weil
2016-04-02 5:54 ` Wido den Hollander
2016-04-02 8:52 ` Loic Dachary
2016-04-04 12:58 ` Wido den Hollander
2016-04-03 12:59 ` Sage Weil
2016-04-04 13:04 ` Wido den Hollander
2016-04-05 8:30 ` Sebastien Han
2016-04-05 9:26 ` Ilya Dryomov
2016-04-05 9:41 ` Wido den Hollander
2016-04-05 10:21 ` Loic Dachary
[not found] ` <CAJ3CzQWJnC7O6pcAF57MqYXMyZEpZVUSWhfynb6yue2iLKXfLA@mail.gmail.com>
2016-04-05 13:26 ` Ilya Dryomov
[not found] ` <CAJ3CzQUWyF-B6o5wBmJ0rcfK_aBkmSX7LcRDkLj=W5COSbPwnQ@mail.gmail.com>
2016-04-05 14:42 ` Ilya Dryomov
2016-04-07 9:26 ` Lars Marowsky-Bree [this message]
2016-04-07 10:31 ` Sebastien Han
2016-04-07 10:51 ` Lars Marowsky-Bree
2016-04-07 11:45 ` Loic Dachary
2016-04-04 0:41 ` Adrian Saul
2016-04-07 12:10 ` Alfredo Deza
2016-06-23 15:41 ` Sage Weil
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=20160407092627.GE26235@suse.de \
--to=lmb@suse.com \
--cc=ceph-devel@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.