Skip to content

[ML] Change the list of MKL libraries we redistribute #2126

Closed
@droberts195

Description

@droberts195

In our build setup instructions we specify the MKL libraries that we will redistribute, for example on Linux:

ml-cpp/build-setup/linux.md

Lines 280 to 285 in e262592

sudo cp /opt/intel/mkl/lib/intel64/libmkl_intel_lp64.so /usr/local/gcc103/lib
sudo cp /opt/intel/mkl/lib/intel64/libmkl_core.so /usr/local/gcc103/lib
sudo cp /opt/intel/mkl/lib/intel64/libmkl_def.so /usr/local/gcc103/lib
sudo cp /opt/intel/mkl/lib/intel64/libmkl_gnu_thread.so /usr/local/gcc103/lib
sudo cp /opt/intel/mkl/lib/intel64/libmkl_avx*.so /usr/local/gcc103/lib
sudo cp /opt/intel/mkl/lib/intel64/libmkl_vml*.so /usr/local/gcc103/lib

Based on the information in the "Computational Layer" section of the table in http://portal.nacad.ufrj.br/online/intel/mkl/common/mkl_userguide/GUID-C823F752-DDA3-4EFB-B673-222C2720FAFA.htm, the subset of libraries we are shipping is not quite correct.

We claim that our code will run on processors that support at minimum SSE4.2 instructions. This means that we should be shipping libmkl_mc3.so in addition to the libraries we are currently shipping. Additionally, since we won't run on processors that support a maximum of SSSE3 nor Hi-k Core 2 processors (from 2009), we don't need to ship libmkl_vml_mc.so nor libmkl_vml_mc2.so.

We should correct this next time we upgrade PyTorch and have to revisit the PyTorch dependencies.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions