From: Loic Dachary <loic@dachary.org>
To: Gregory Farnum <greg@gregs42.com>
Cc: "Deneau, Tom" <tom.deneau@amd.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: erasure pool with isa plugin
Date: Tue, 23 Jun 2015 06:15:03 -0400 [thread overview]
Message-ID: <558931A7.9040501@dachary.org> (raw)
In-Reply-To: <CAC6JEv-qmFCwf1rdE6KnzcE=qQNgZr3AYpHwZ0OBNj2wcteSog@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
Hi,
On 23/06/2015 06:06, Gregory Farnum wrote:
> On Mon, Jun 22, 2015 at 10:34 PM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Tom,
>>
>> On 22/06/2015 17:10, Deneau, Tom wrote:
>>> If one has a cluster with some nodes that can run with the ISA plugin
>>> and some that cannot, is there a way to define a pool such that the
>>> ISA-capable nodes can use the ISA plugin and the others can use say
>>> the jerasure plugin?
>>
>> There is no way to do that, because there is no guarantee that an object encoded by jerasure can be decoded by isa and vice versa.
>
> Shouldn't we be able to set up something that *does* guarantee that,
> though? Either by combining them into a single plugin which
> dynamically configures to the fastest possible for that machine, or by
> running them against the same object corpus and requiring that they
> produce the same output?
I don't know enough about the maths involved to evaluate how difficult it is. Although both implement Reed Solomon using Vandermonde or Cauchy matrices, I think there are details that makes the output different.
Cheers
> -Greg
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2015-06-23 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 21:10 erasure pool with isa plugin Deneau, Tom
2015-06-22 21:34 ` Loic Dachary
2015-06-23 10:06 ` Gregory Farnum
2015-06-23 10:15 ` 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=558931A7.9040501@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@gregs42.com \
--cc=tom.deneau@amd.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.