On 07/11/2015 12:35 AM, Dmitry Smirnov wrote:
On Thu, 9 Jul 2015 23:48:32 Loic Dachary wrote:
It so happens that I don't have time to do team work on
this, hence my proposal to take over if the package was orphaned.
No time for team work?!? Please enlighten us about your plans to fix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 09/07/15 22:27, Thomas Goirand wrote:
One of the reasons why I like standalone library is that it can
run its own
tests as well -- a something rarely seen in bundled (statically
linked) libraries. Unfortunately at the moment libjerasure
On Thu, 9 Jul 2015 23:48:32 Loic Dachary wrote:
It so happens that I don't have time to do team work on
this, hence my proposal to take over if the package was orphaned.
No time for team work?!? Please enlighten us about your plans to fix
everything single-handedly as soon as those pesky
On 07/08/2015 03:07 PM, Dmitry Smirnov wrote:
On Wed, 8 Jul 2015 11:07:43 Loic Dachary wrote:
Without integration tests, linking Ceph against the wrong jerasure version
may lead to data loss. Prior to publishing a Ceph version, various
integration tests run to verify encoding / decoding,
On 07/08/2015 03:57 PM, Loic Dachary wrote:
The other reason is that
jerasure can be optimized for SIMD instructions (ARM / INTEL) and not
doing so significantly impacts performances.
Once again, this seems to be an improvement suggestion for libjerasure
rather
than argument against using
Hi Thomas,
I'm offering my help, this is positive :-) I'm sure you're very reactive in
maintaining the package, no question about it. My offer relates to solving data
integrity potential problems, integration testing as well as code optimization.
It so happens that I don't have time to do team
Hi,
Without integration tests, linking Ceph against the wrong jerasure version may
lead to data loss. Prior to publishing a Ceph version, various integration
tests run to verify encoding / decoding, this is the main incentive to have
jerasure as part of Ceph. The other reason is that jerasure
Hi Dmitry,
On 08/07/2015 15:07, Dmitry Smirnov wrote:
On Wed, 8 Jul 2015 11:07:43 Loic Dachary wrote:
Without integration tests, linking Ceph against the wrong jerasure version
may lead to data loss. Prior to publishing a Ceph version, various
integration tests run to verify encoding /
On Wed, 8 Jul 2015 11:07:43 Loic Dachary wrote:
Without integration tests, linking Ceph against the wrong jerasure version
may lead to data loss. Prior to publishing a Ceph version, various
integration tests run to verify encoding / decoding,
Those check are part of post-build tests, right?
On 07/06/2015 04:46 PM, Gaudenz Steinlin wrote:
[ Adding the jerasure maintainer to the CC ]
Hi
Loic Dachary l...@dachary.org writes:
Hi,
I'm co-maintainer of both jerasure and ceph. If the Debian jerasure
package was orphaned, I would be happy to step in and maintain it as a
[ Adding the jerasure maintainer to the CC ]
Hi
Loic Dachary l...@dachary.org writes:
Hi,
I'm co-maintainer of both jerasure and ceph. If the Debian jerasure
package was orphaned, I would be happy to step in and maintain it as a
standalone package. Jerasure was packaged without dialog
11 matches
Mail list logo
