All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Andreas-Joachim Peters <andreas.joachim.peters@cern.ch>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Checking of Reed-Solomon Vandermonde parameter combinations
Date: Thu, 03 Jul 2014 12:22:00 +0200	[thread overview]
Message-ID: <53B52EC8.5030708@dachary.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]

Hi Andreas,

There are some combinations of K/M parameters for which Reed-Solomon Vandermonde may not be able to recover from the loss of M chunks. Reed-Solomon Cauchy does not suffer from this problem. (I'm paraphrasing a conversation we had in private, feel free to correct me if I'm wrong).

In the context of Ceph we are interested in a limited range of parameters so I ran a test with:

https://github.com/ceph/ceph/blob/master/src/test/erasure-code/ceph_erasure_code_benchmark.cc#L40

for k in $(seq 2 50) ; do for m in $(seq 1 $k) ; do echo -n "k=$k m=$m " ; ./ceph_erasure_code_benchmark      --plugin jerasure      --parameter directory=.libs      --parameter technique=reed_sol_van      --parameter k=$k      --parameter m=$m --erasures $m      --iterations 1 --workload decode ; done ; done

and it does not throw an error. It basically take a range of parameters K=2,M=2 up to K=50,M=50 and decode with M erasures for each of them. Should some of them fail ?

Cheers
-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

             reply	other threads:[~2014-07-03 10:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 10:22 Loic Dachary [this message]
2014-07-03 10:27 ` Checking of Reed-Solomon Vandermonde parameter combinations Andreas Joachim Peters
2014-07-03 10:30   ` 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=53B52EC8.5030708@dachary.org \
    --to=loic@dachary.org \
    --cc=andreas.joachim.peters@cern.ch \
    --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.