[
https://issues.apache.org/jira/browse/YETUS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15247687#comment-15247687
]
Kai Zheng commented on YETUS-222:
---------------------------------
Thanks [~busbey] for taking care of this, [~cmccabe] and [~aw] for the great
discussions!
As I said here or elsewhere before, the ISA-L team is working on packaging
stuffs on more platforms, and as you might understand, this will take some time
to happen. I will provide the update and check the integration accordingly.
Intel ISA-L does support these platforms: Linux, Windows, FreeBSD and Mac.
These are the ones tested but others likely work such as Solaris, etc. This
means the library can run and function on these platforms, regardless of the
underlying arch being x86 or not. Surely it will perform best on x86
architectures, but will fall back and still perform better than pure Java
implementations. The optimization and arch detecting stuffs are handled in the
library itself, I don't think we need to care about it here. I may
misunderstand YETUS and the task, but I guess it's only for project
development, building and testing? The users should be developers as we are,
and the running environment should be limited to ubuntu, centos and mac? I'm
not sure about we're going to run the scripts in specific architectures like
AMD, ARM and etc. as mentioned above? I'm not a hardware person, but we're
surely not developing a library like ISA-L and we'd better not couple with the
specifics in the high level.
{{liberasurecode}} is mentioned and seems to be proposed as an alternative
approach to avoid introducing ISA-L directly. I checked liberasurecode and it
attempted to support back ends like ISA-L. It looks good to support more
options other than ISA-L, but I don't see any other better option it supports
actually. Furthermore, how it will solve the concern and problem we're
discussing about here? With any real back end is used, we'll still need to
worry about the packaging and testing stuffs.
So in summary, there may be two things for ISA-L: 1) for test and developer,
need to provide RPM like package installations on developer friendly and
Jenkins target platforms; 2) for end users continue to accept feedback and
provide supports on more runtime platforms Hadoop can run. For this issue, if
we'd like to close it as won't fix, maybe it won't be bad to have it pending
more time.
Thanks for the agreement. Hope this helps.
> hadoop: add ISA-L support
> -------------------------
>
> Key: YETUS-222
> URL: https://issues.apache.org/jira/browse/YETUS-222
> Project: Yetus
> Issue Type: Improvement
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Kai Zheng
> Attachments: YETUS-222-v1.patch, YETUS-222-v2.patch
>
>
> Hadoop personality should support building the native code under Jenkins when
> Docker is invoked.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
