Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #13630 > unrolled thread

Why is isal limited to just three archs?

Back to article view | Back to linux.debian.maint.python

Contents

  Why is isal limited to just three archs? Nilesh Patra <nilesh@nileshpatra.info> - 2021-10-16 09:10 +0200
    Re: Why is isal limited to just three archs? Thomas Goirand <zigo@debian.org> - 2021-10-16 10:50 +0200
      Re: Why is isal limited to just three archs? Graham Inggs <ginggs@debian.org> - 2021-10-16 12:40 +0200
        Re: Why is isal limited to just three archs? Nilesh Patra <nilesh@nileshpatra.info> - 2021-10-17 14:00 +0200
      Re: Why is isal limited to just three archs? Gregor Riepl <onitake@gmail.com> - 2021-10-16 12:50 +0200
    Re: Why is isal limited to just three archs? Ondrej Novy <novy@ondrej.org> - 2021-10-28 19:20 +0200

#13630 — Why is isal limited to just three archs?

[Multipart message — attachments visible in raw view] — view raw

Hi Ondřej,

I see that isal package is limited to amd64, arm64 and kfreebsd-amd64.
Is there a particular reason for this? -- Is it possible to extend support to other archs?

Actually, a -med team package fastp has started to depend on libisal-dev, and this
now is limited to the few archs isal supports. So it would be really nice if isal
can build on more archs.

Please do let me know.

Nilesh

[toc] | [next] | [standalone]

#13631

On 10/16/21 9:09 AM, Nilesh Patra wrote:
> Hi Ondřej,
> 
> I see that isal package is limited to amd64, arm64 and kfreebsd-amd64.
> Is there a particular reason for this? -- Is it possible to extend
> support to other archs?
> 
> Actually, a -med team package fastp has started to depend on
> libisal-dev, and this
> now is limited to the few archs isal supports. So it would be really
> nice if isal
> can build on more archs.
> 
> Please do let me know.
> 
> Nilesh

Hi,

Did you look into the source package? isal is written in assembly
language...

Cheers,

Thomas Goirand (zigo)

[toc] | [prev] | [next] | [standalone]

#13632

Hi

On Sat, 16 Oct 2021 at 10:42, Thomas Goirand <zigo@debian.org> wrote:
>
> On 10/16/21 9:09 AM, Nilesh Patra wrote:
> > Hi Ondřej,
> >
> > I see that isal package is limited to amd64, arm64 and kfreebsd-amd64.
> > Is there a particular reason for this? -- Is it possible to extend
> > support to other archs?
> >
> > Actually, a -med team package fastp has started to depend on
> > libisal-dev, and this
> > now is limited to the few archs isal supports. So it would be really
> > nice if isal
> > can build on more archs.
> >
> > Please do let me know.
> >
> > Nilesh
>
> Hi,
>
> Did you look into the source package? isal is written in assembly
> language...
>
> Cheers,
>
> Thomas Goirand (zigo)

I see at least an erasure_code/ppc64le directory.

I did a quick test build in Ubuntu and the package built and passed
its tests on armhf, ppc64el and riscv64, failing only because of
missing symbols.  Perhaps the reduced libisal2.symbols.arm64 can be
used for other architectures as well?

Regards
Graham

[toc] | [prev] | [next] | [standalone]

#13634

[Multipart message — attachments visible in raw view] — view raw

Hi Thomas,

On 10/16/21 4:07 PM, Graham Inggs wrote:
>> Hi,
>>
>> Did you look into the source package? isal is written in assembly
>> language...
> I see at least an erasure_code/ppc64le directory.
> 
> I did a quick test build in Ubuntu and the package built and passed
> its tests on armhf, ppc64el and riscv64, failing only because of
> missing symbols.  Perhaps the reduced libisal2.symbols.arm64 can be
> used for other architectures as well?

After Graham's tests, would it be possible to extend the arch list?
I could help test it across more archs if you would like -- porter boxes to rescue :)

Nilesh

[toc] | [prev] | [next] | [standalone]

#13633

> Did you look into the source package? isal is written in assembly
> language...

That doesn't seem quite right.
The readme states:

> other:
>
> Compiler: Portable base functions are available that build with most C
> compilers.

And it does look like there are corresponding .c implementations, at
least for some of the functions.

Not sure about source or binary compatibility, though.

[toc] | [prev] | [next] | [standalone]

#13664

[Multipart message — attachments visible in raw view] — view raw

Hi Nilesh,

so 16. 10. 2021 v 9:09 odesílatel Nilesh Patra <nilesh@nileshpatra.info>
napsal:

> I see that isal package is limited to amd64, arm64 and kfreebsd-amd64.
> Is there a particular reason for this? -- Is it possible to extend support
> to other archs?
>

When I packed libisal, only "customer" was liberasurecode. Liberasurecode
supports many backends and supports all archs. And because libisal is
highly optimized for ARM and amd64, I built it only for these archs. Other
platforms are supported, but not optimized. liberasurecode directly should
perform better.

Actually, a -med team package fastp has started to depend on libisal-dev


And because there is other "customer", I will try to build it for all
archs.

Thanks.

-- 
Best regards
 Ondřej Nový

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web