MKL - Revision history

Edward at 14:29, 6 June 2019

2019-06-06T14:29:19Z

Jdesjard at 13:52, 2 November 2017

2017-11-02T13:52:55Z

Ppomorsk: /* Version Selection */ update

2016-07-25T19:00:56Z

‎Version Selection: update

Roberpj: /* References */

2015-04-28T18:55:27Z

‎References

Roberpj: /* References */

2015-04-28T18:44:47Z

‎References

Ppomorsk: /* General Notes */

2014-11-19T19:42:02Z

‎General Notes

Ppomorsk: /* General Notes */ update

2014-11-19T19:39:03Z

‎General Notes: update

Ppomorsk at 19:29, 19 November 2014

2014-11-19T19:29:08Z

Ppomorsk: /* General Notes */ compile script discontinued

2014-11-19T19:25:12Z

‎General Notes: compile script discontinued

Ppomorsk: color

2014-11-19T19:23:41Z

color

← Older revision		Revision as of 14:29, 6 June 2019
Line 1:		Line 1:
		+	{{Template:CCMissing}}
	{{Template:GrahamUpdate}}		{{Template:GrahamUpdate}}
	{{Software		{{Software

← Older revision		Revision as of 13:52, 2 November 2017
Line 1:		Line 1:
		+	{{Template:GrahamUpdate}}
	{{Software		{{Software
	\|package_name=MKL		\|package_name=MKL

← Older revision		Revision as of 19:00, 25 July 2016
Line 14:		Line 14:

	Presently the version of MKL 10.3.9 is the default and its module (mkl/10.3.9) is loaded automatically when you login. Version 11.1.4 is also available (mkl/11.1.4)		Presently the version of MKL 10.3.9 is the default and its module (mkl/10.3.9) is loaded automatically when you login. Version 11.1.4 is also available (mkl/11.1.4)
		+
		+	Later versions of MKL are bundled with the Intel compiler. You can still load them separately (for use with different compiler) by loading modules: intel/mkl/15.0.3, intel/mkl/15.0.6, intel/mkl/16.0.3.

	More details about module usage can be found here:		More details about module usage can be found here:

← Older revision		Revision as of 18:55, 28 April 2015
Line 428:		Line 428:
	o Use of Intel MKL data types in C/C++ applications<br>		o Use of Intel MKL data types in C/C++ applications<br>
	http://software.intel.com/en-us/articles/use-of-intel-mkl-data-types-in-cc-applications		http://software.intel.com/en-us/articles/use-of-intel-mkl-data-types-in-cc-applications
		+
		+	o Working with the Intel® Math Kernel Library Cluster Software<br>
		+	https://software.intel.com/en-us/node/528420

@@ Line 424: / Line 424: @@
 o Using the ILP64 Interface vs. LP64 Interface<br>
-http://software.intel.com/sites/products/documentation/hpc/mkl/mkl_userguide_lnx/GUID-87821148-338B-4022-8C90-F24C866F2878.htm
+https://software.intel.com/en-us/node/528682
 o Use of Intel MKL data types in C/C++ applications<br>
 http://software.intel.com/en-us/articles/use-of-intel-mkl-data-types-in-cc-applications

@@ Line 236: / Line 236: @@
 ====COMPILING WITH MKL - USING ONLINE LINK ADVISOR====
-More generally (on any SHARCNET cluster) the <i>Intel Math Kernel Library Link Line Advisor</i> http://software.intel.com/en-us/articles/intel-mkl-link-line-advisor/ can be used to generate linker options for more complex linking situations with MKL.  For instance, to determine the link arguments for the MKL version 10.3, Linux Operating System, Intel Compiler, Intel (R) 64 architecture, Static Linking, 32 bit Integers, sequential version of MKL, ScaLAPACK library, and OpenMPI, the MKL Link Line Advisor would return the following linking recomendation:
+More generally (on any SHARCNET cluster) the <i>Intel Math Kernel Library Link Line Advisor</i> http://software.intel.com/en-us/articles/intel-mkl-link-line-advisor/ can be used to generate linker options for more complex linking situations with MKL.  For instance, to determine the link arguments for the MKL version 10.3, Linux Operating System, Intel Compiler, Intel (R) 64 architecture, Static Linking, 32 bit Integers, sequential version of MKL, ScaLAPACK library, and OpenMPI, the MKL Link Line Advisor would return the following linking recomendation (the syntax below would go into your [[Make utility and makefiles|Makefile]]):
 <pre>

@@ Line 236: / Line 236: @@
 ====COMPILING WITH MKL - USING ONLINE LINK ADVISOR====
-More generally (on any sharcnet cluster) the <i>Intel Math Kernel Library Link Line Advisor</i> http://software.intel.com/en-us/articles/intel-mkl-link-line-advisor/ can be used to generate linker options for more complex linking situations with MKL than the compile script supports.  For instance, to determine the link arguments for the Linux Operating System, IA64 Itanium Processor, Intel Compiler, Dynamic Linking, 64 bit Integers, Multi-threaded Version of MKL, Intel OpenMP Library (libiomp5) plus the Scalapack Library, the MKL Link Line Advisor would (at the time of this writing) return the following recomendation:
+More generally (on any SHARCNET cluster) the <i>Intel Math Kernel Library Link Line Advisor</i> http://software.intel.com/en-us/articles/intel-mkl-link-line-advisor/ can be used to generate linker options for more complex linking situations with MKL.  For instance, to determine the link arguments for the MKL version 10.3, Linux Operating System, Intel Compiler, Intel (R) 64 architecture, Static Linking, 32 bit Integers, sequential version of MKL, ScaLAPACK library, and OpenMPI, the MKL Link Line Advisor would return the following linking recomendation:
 <pre>
-$MKLPATH/libmkl_scalapack_lp64.a $MKLPATH/libmkl_solver_lp64.a -Wl,--start-group $MKLPATH/libmkl_intel_lp64.a $MKLPATH/libmkl_intel_thread.a $MKLPATH/libmkl_core.a $MKLPATH/libmkl_blacs_sgimpt_lp64.a -Wl,--end-group -openmp -lpthread
+$(MKLROOT)/lib/intel64/libmkl_scalapack_lp64.a -Wl,--start-group $(MKLROOT)/lib/intel64/libmkl_intel_lp64.a $(MKLROOT)/lib/intel64/libmkl_core.a $(MKLROOT)/lib/intel64/libmkl_sequential.a -Wl,--end-group $(MKLROOT)/lib/intel64/libmkl_blacs_openmpi_lp64.a -lpthread -lm
 </pre>
-The MKLPATH should be set accordingly to which version of the intel compiler module is loaded as well as the type of operating system.  For instance:
+and the following recommendation for locating the include files
 <pre>
-export MKLPATH=/opt/sharcnet/intel/11.0.083/ifc/mkl/lib/em64t
+ -I$(MKLROOT)/include
 </pre>
-o Centos6 With Default 12.1.3 Compiler Use:
+The $(MKLROOT) will already be set for you by the MKL module which is currently loaded.  The above case is the one applicable on most SHARCNET clusters.
-<pre>
-export MKLPATH=/opt/sharcnet/mkl/10.3.9/mkl/lib/intel64
-</pre>
 ====Using The ILP64 Vs LP64 Variants Of MKL====

@@ Line 24: / Line 24: @@
 ===Examples of Job Compilation===
 We are assuming that the following modules are currently loaded:  mkl/10.3.9  intel/12.1.3
-==== fortran dgemm example====
 Use following command to compile file test_dgemm.f90:
@@ Line 91: / Line 92: @@
 </source>
-==== fortran zdotc  example====
+==== Fortran ZDOTC  example====
 Use following command to compile:
@@ Line 149: / Line 150: @@
-==== c zdotc  example====
+==== C ZDOTC  example====
 Use following command to compile:

← Older revision		Revision as of 19:25, 19 November 2014
Line 232:		Line 232:

	===General Notes===		===General Notes===
−	~~====Linking to MKL on Centos5 Clusters====~~
−	On the remaining centos5 clusters (see https://www.sharcnet.ca/my/software/show/129) the compile script can be used for codes needing to link with the MKL blas and lapack libraries (where the program extension <b>xyz</b> can be any of c/cc, cxx/CC/c++ or f77/f90/f95) as follows:
−
−	~~<pre>compile program.xyz -llapack</pre>~~
−
−	~~To demonstrate this approach, consider the following example where the result from a.out can be compared with the expect vendor provided solution:~~
−
−	~~<pre>~~
−	~~ssh kraken.sharcnet.ca~~
−	~~ln -s /opt/sharcnet/acml/4.3.0/ifort-64bit/ifort64/examples/dgetrf_example.f~~
−	~~compile dgetrf_example.f -llapack~~
−	~~./a.out~~
−	~~cat /opt/sharcnet/acml/4.3.0/ifort-64bit/ifort64/examples/dgetrf_example.expected~~
−	~~</pre>~~

	====COMPILING WITH MKL - USING ONLINE LINK ADVISOR====		====COMPILING WITH MKL - USING ONLINE LINK ADVISOR====

@@ Line 26: / Line 26: @@
 ==== fortran dgemm example====
 Use following command to compile file test_dgemm.f90:
   $FC test_dgemm.f90 -L$MKLROOT/lib/intel64 -lmkl_intel_lp64 -lmkl_core -lmkl_intel_thread -lpthread -lm -openmp
 where
@@ Line 89: / Line 93: @@
 ==== fortran zdotc  example====
 Use following command to compile:
   $FC fortran_zdotc.f90 -L$MKLROOT/lib/intel64 -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_core -openmp -lpthread
 where
@@ Line 143: / Line 151: @@
 ==== c zdotc  example====
 Use following command to compile:
    $CC main_zdotc.c -L$MKLROOT/lib/intel64 -lmkl_intel_lp64 -lmkl_intel_thread -lmkl_core -openmp -lpthread
 where
 <source lang="c">
   /* file name = main_zdotc.c */