Intel® oneAPI Math Kernel Library
Ask questions and share information with other developers who use Intel® Math Kernel Library.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
7234 Discussions

ZYTRI sequential?

Olaf_Schenk
Beginner
‎07-17-2015 07:26 AM
794 Views

Hi
I am testing the following code with composer_xe_2015

lwork = 256*n
call ZSYTRF( 'U', n, afull, n, ipiv, work, lwork, error )
call ZSYTRI( 'U', n, afull, n, ipiv, work, lwork, error )

using

gfortran -O3 -fopenmp  read_blas.f90 -Wl,--start-group ${MKLROOT}/lib/intel64/libmkl_gf_lp64.a ${MKLROOT}/lib/intel64/libmkl_core.a ${MKLROOT}/lib/intel64/libmkl_gnu_thread.a -Wl,--end-group -ldl -lpthread -lm

After setting OMP_NUM_THREADS=16 I can see in "top" that  ZSYTRF runs in parallel but ZSYTRI not. The matrix is large enough (n=15120)

Any idea how to solve this problem?

Olaf

 

 

 

 

0 Kudos

Link Copied

1 Reply
Ying_H_Intel
Moderator
‎07-19-2015 08:00 PM
794 Views

Hi Olaf

You are right, the function is not threaded. Here is threaded function list for your reference. 

https://software.intel.com/en-us/articles/intel-mkl-threaded-functions/

As i understand, you actually expect the function is parallel so improve the performance, right?  If yes, could you please let me know some information, like background, problem size, hardware etc. If private information, you may reply me by Private message. 

Thanks

Ying 

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.