All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Kevin Greenan <kmgreen2@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: jerasure / gf-complete & 32 bits
Date: Sat, 29 Mar 2014 10:08:51 +0100	[thread overview]
Message-ID: <53368DA3.7080206@dachary.org> (raw)
In-Reply-To: <5335AE3D.1050104@dachary.org>

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

The gf-complete + jerasure tests run fine on Ubuntu saucy 32 bits. The problem is when trying to compile on a 32 bits machine as shown here

http://gitbuilder.sepia.ceph.com/gitbuilder-ceph-tarball-precise-i386-basic/log.cgi?log=cb624fc9ed1e891e51cc0d20622d43f6fcd08cd5


On 28/03/2014 18:15, Loic Dachary wrote:
> Hi Kevin,
> 
> Someone mentionned a problem (no more information at the moment ;-) about running jerasure / gf-complete on a 32 bits machine. Does that ring a bell ? I'll try it out with the test method you suggested:
> 
> "'gf_methods <w> -A -U' to run all of the tests for w=[4,8,16,32,64,128]. Then, I install a fresh Jerasure and run test_all_gfs.sh and time_all_gfs_argv_init.sh. Finally, I install PyECLib (Python library that wraps Jerasure, ISA-L (soon) and has some homegrown XOR- codes) and run the scripts under tests/."
> 
> Cheers
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


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

  reply	other threads:[~2014-03-29  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 17:15 jerasure / gf-complete & 32 bits Loic Dachary
2014-03-29  9:08 ` Loic Dachary [this message]
2014-03-29 16:16   ` Kevin Greenan
2014-03-29 21:38     ` Loic Dachary
2014-03-30 14:58       ` Justin Erenkrantz
2014-03-30 16:01         ` 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=53368DA3.7080206@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=kmgreen2@gmail.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.