All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Samuel Just <sjust@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
	"Miyamae, Takeshi" <miyamae.takeshi@jp.fujitsu.com>
Subject: Erasure Code Plugins : PLUGINS_V3 feature
Date: Wed, 29 Jul 2015 11:16:43 +0200	[thread overview]
Message-ID: <55B899FB.4080007@dachary.org> (raw)

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

Hi Sam,

The SHEC plugin[0] has been running in the rados runs[1] in the past few months. It also has a matching corpus verification which runs on every make check[2] as well as its optimized variants. I believe the flag "experimental" can now be removed. 

In order to do so, we need to use a PLUGINS_V3 feature, in the same way we did back in Giant when the ISA and LRC plugins were introduced[3]. This won't be necessary in the future, when there is a generic plugin mechanism, but right now that's what we need. It would be a commit very similar to the one implementing PLUGINS_V2[4].

Is this agreeable to you ? Or would you rather see another way to resolve this ?

Cheers

[0] https://github.com/ceph/ceph/tree/master/src/erasure-code/shec
[1] https://github.com/ceph/ceph-qa-suite/tree/master/suites/rados/thrash-erasure-code-shec
[2] https://github.com/ceph/ceph-erasure-code-corpus/blob/master/v0.92-988/non-regression.sh#L52
[3] http://tracker.ceph.com/issues/9343
[4] https://github.com/ceph/ceph/commit/9687150ceac9cc7e506bc227f430d4207a6d7489

-- 
Loïc Dachary, Artisan Logiciel Libre


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

             reply	other threads:[~2015-07-29  9:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  9:16 Loic Dachary [this message]
2015-08-05  8:21 ` Erasure Code Plugins : PLUGINS_V3 feature Loic Dachary
2015-08-05 18:44   ` Sage Weil
2015-08-06  0:28     ` Miyamae, Takeshi
2015-08-06 13:57       ` Loic Dachary
2015-08-07  5:12         ` Miyamae, Takeshi

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=55B899FB.4080007@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=miyamae.takeshi@jp.fujitsu.com \
    --cc=sjust@redhat.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.