From: Loic Dachary <loic@dachary.org>
To: Alex Elsayed <eternaleye@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Erasure code library summary
Date: Wed, 19 Jun 2013 08:56:06 +0200 [thread overview]
Message-ID: <51C15606.4010105@dachary.org> (raw)
In-Reply-To: <kpr0dn$3cr$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
On 06/19/2013 03:10 AM, Alex Elsayed wrote:
> Loic Dachary wrote:
>
>> Hi Ceph,
>>
> <snip>
>> Reed-Solomon coding family is the only one that can keep the chuncks
>> unencoded and therefore concatenable.
> <snip>
>
> In my understanding, this is not strictly true - any 'systematic' code will
> have the unencoded chunks remain available in this manner, and any non-
> systematic linear code can be transformed into a systematic code with the
> same minimum distance. Fountain codes are often explicitly constructed to
> maintain this property, as in the case of RaptorQ [RFC 6330].
>
> https://en.wikipedia.org/wiki/Systematic_code
Thanks for correcting my mistake :-)
>
> --
> 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
--
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 prev parent reply other threads:[~2013-06-19 6:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 12:22 Erasure code library summary Loic Dachary
2013-06-19 1:10 ` Alex Elsayed
2013-06-19 1:14 ` Alex Elsayed
2013-06-19 7:00 ` Loic Dachary
2013-06-19 7:47 ` Alex Elsayed
2013-06-19 8:33 ` Loic Dachary
2013-06-19 9:09 ` Alex Elsayed
2013-06-19 10:41 ` Loic Dachary
2013-06-19 6:56 ` Loic Dachary [this message]
2013-06-19 11:33 ` Mark Nelson
2013-06-19 12:10 ` Loic Dachary
2013-06-19 12:33 ` Mark Nelson
2013-06-23 7:01 ` 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=51C15606.4010105@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=eternaleye@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.