CEPH filesystem development
 help / color / mirror / Atom feed
From: Marcus Watts <mwatts@redhat.com>
To: ceph-devel@vger.kernel.org
Subject: ceph / rocksdb
Date: Wed, 24 Feb 2016 01:05:46 -0500	[thread overview]
Message-ID: <20160224060546.GC6585@degu.b.linuxbox.com> (raw)

So, about that rocksdb thing.

Rocksdb ships with 2 build systems:
	cmake		- windows only
	make based	- everything else

The makefile is very "retro".  Um.  Let's just leave it there.

The cmake part was more interesting; the main problem it had
was it was *way* too windows specific.  Which is actually kinda
hard to do, since that's just what cmake wasn't supposed to be.

Building rocksdb (-g) takes about 1g of build tree space,
and running "make check" on it takes about half an hour.
I really don't want to slow down my ceph builds this way,
so rather than make rocksdb with the rest of ceph, I would
much rather it be packaged / installed separately.

So I put together:
a set of changes to build rocksdb with cmake on linux
an rpm .spec file to build it for fedora.

Rpms (source & amd64) can be found here:
	http://people.redhat.com/mwatts/rocksdb/
and a git repo with the cmake changes here,
	https://github.com/mdw-at-linuxbox/rocksdb

The cmake parts could certainly still use more work; I haven't
tested this and it will probably need changes on anything other
than x86_64, such as certainly any non-gcc/non-linux platform.

					-Marcus Watts

             reply	other threads:[~2016-02-24  6:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  6:05 Marcus Watts [this message]
2016-02-24 17:58 ` ceph / rocksdb Ken Dreyer
2016-02-24 18:04   ` Allen Samuels
2016-02-24 18:06   ` Sage Weil
2016-02-25  8:15     ` Marcus Watts
2016-02-25 20:21   ` Nathan Cutler
2016-06-06 10:05     ` Willem Jan Withagen
2016-06-06 10:43       ` Nathan Cutler
2016-06-06 12:26       ` Sage Weil
2016-06-06 12:29         ` Willem Jan Withagen

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=20160224060546.GC6585@degu.b.linuxbox.com \
    --to=mwatts@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox