From mboxrd@z Thu Jan 1 00:00:00 1970 From: Loic Dachary Subject: fecpp C++ forward error correction library Date: Mon, 22 Apr 2013 15:19:19 +0200 Message-ID: <517538D7.6050706@dachary.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigDC933155AB912A403783F9A9" Return-path: Received: from smtp.dmail.dachary.org ([86.65.39.20]:40022 "EHLO smtp.dmail.dachary.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753682Ab3DVNTV (ORCPT ); Mon, 22 Apr 2013 09:19:21 -0400 Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Christopher LILJENSTOLPE Cc: Ceph Development , Jack Lloyd This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDC933155AB912A403783F9A9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Christopher, Jack Lloyd is the author of fecpp ( http://www.randombit.net/code/fecpp/ = ) and he tells me someone sent him a new SIMD approach a few weeks ago. I= 'm not sure what SIMD means yet, but I'll figure it out ;-). I tend to fa= vor fecpp because it is more self contained and may be easier to embed th= an https://pypi.python.org/pypi/zfec Cheers --=20 Lo=EFc Dachary, Artisan Logiciel Libre --------------enigDC933155AB912A403783F9A9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlF1ONcACgkQ8dLMyEl6F22oUQCeNCnZzjD1umKvjxLhF8ZcODH7 QsoAnixmKJdMPJMIgqKbexpFAnnCCUOK =GSMN -----END PGP SIGNATURE----- --------------enigDC933155AB912A403783F9A9--