From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Erasure Code plugin system with an example : review request
Date: Tue, 20 Aug 2013 13:55:29 +0200 [thread overview]
Message-ID: <52135931.3040601@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
Hi Ceph,
Yesterday I implemented a simple erasure code plugin that can sustain the loss of a single chunk.
https://github.com/dachary/ceph/blob/wip-5878/src/osd/ErasureCodeExample.h
and it works as shown in the unit test
https://github.com/dachary/ceph/blob/wip-5878/src/test/osd/TestErasureCodeExample.cc
It would be of limited use in a production environment because it only saves 25% space ( M=2 K=1 ) over a 2 replica pool, but it would work.
I would very much appreciate a review of the erasure code plugin system and the associated example plugin :
https://github.com/ceph/ceph/pull/515
When it's good enough, creating a jerasure plugin will be next :-)
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
All that is necessary for the triumph of evil is that good people do nothing.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
reply other threads:[~2013-08-20 11:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52135931.3040601@dachary.org \
--to=loic@dachary.org \
--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.