From: Loic Dachary <loic@dachary.org>
To: Koleos Fuscus <koleosfuscus@gmail.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: coefficients
Date: Fri, 11 Jul 2014 20:19:39 +0300 [thread overview]
Message-ID: <53C01CAB.5070208@dachary.org> (raw)
In-Reply-To: <CACUN8h2ixhb_yDq2mY=zMW=GPUV-wDEzkGLG9LVh-d3VT-2Hxg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Hi koleosfuscus,
Thanks for the pointer, it is very helpful. I'm inclined to keep the simpler approach for the first implementation while exploring and learning more about the smarter / more complex approach. This may change if someone willing to help comes on board in the meantime ;-)
Cheers
On 11/07/2014 13:48, Koleos Fuscus wrote:
> Hi Loic,
>
> If you still need to calculate more coefficients there is an
> explanation of how to construct the coding equations in the paper
> Erasure coding in Windows Azure Storage (unless you will keep your LRC
> implementation simple and do only the LRC (10,6,5) ). I undertand that
> the codes LRC in the mentioned paper are not exactly the same but at
> least the paper explains the coefficients. I think in Azure they used
> functional repair instead of exact repair as you wish.
>
> koleosfuscus
>
> ________________________________________________________________
> "My reply is: the software has no known bugs, therefore it has not
> been updated."
> Wietse Venema
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2014-07-11 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 10:48 coefficients Koleos Fuscus
2014-07-11 17:19 ` Loic Dachary [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=53C01CAB.5070208@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=koleosfuscus@gmail.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.