From: Loic Dachary <loic@dachary.org>
To: Pierre Evenou <pierre.evenou@rozofs.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Mojette Transform implementation
Date: Wed, 29 May 2013 13:18:32 +0200 [thread overview]
Message-ID: <51A5E408.6070104@dachary.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]
Hi Pierre,
As discussed today over the phone, I'm very much interested in trying to reuse the Mojette Transform implementation in the context of the work related to the implementation of an erasure coded backend in Ceph. The progress can be tracked from http://tracker.ceph.com/issues/5046 and the sub-tickets and the original discussion from the last Ceph summit is at http://wiki.ceph.com/01Planning/02Blueprints/Dumpling/Erasure_encoding_as_a_storage_backend
I was reading the code of rbs_restore_one_rb_entry at
https://github.com/rozofs/rozofs/blob/master/src/storaged/rbs.c#L104
and assumed the implementation is in
https://github.com/rozofs/rozofs/blob/master/src/storaged/rbs_transform.h
https://github.com/rozofs/rozofs/blob/master/src/storaged/rbs_transform.cc
And also tried to understand http://en.wikipedia.org/wiki/Mojette_Transform and bought "The Mojette Transform: Theory and Applications" http://eu.wiley.com/WileyCDA/WileyTitle/productCd-1848210809.html in the hope to get more sense out of it ;-)
Is there a part of the rozofs code you would advise me to read first in order to understand how it works ?
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: 262 bytes --]
next reply other threads:[~2013-05-29 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 11:18 Loic Dachary [this message]
[not found] ` <CAD8-Aea7Z0Y40d6hTti_r+MXh0ECWazp1y0m9iYvP30qpX+LbQ@mail.gmail.com>
2013-05-30 15:49 ` Mojette Transform implementation Loic Dachary
2013-05-30 15:56 ` Loic Dachary
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=51A5E408.6070104@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=pierre.evenou@rozofs.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.