-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xsyrk
vs xxsyrk
vs dsyrk
(in netlib LAPACK)
#2405
Comments
Reading MklLapack code you can find template <CpuType cpu>
struct MklLapack<double, cpu>
{
typedef DAAL_INT SizeType;
static void xgetrf(DAAL_INT * m, DAAL_INT * n, double * a, DAAL_INT * lda, DAAL_INT * ipiv, DAAL_INT * info)
{
__DAAL_MKLFN_CALL(lapack_, dgetrf, (m, n, a, lda, ipiv, info));
}
static void xxgetrf(DAAL_INT * m, DAAL_INT * n, double * a, DAAL_INT * lda, DAAL_INT * ipiv, DAAL_INT * info)
{
int old_threads = fpk_serv_set_num_threads_local(1);
__DAAL_MKLFN_CALL(lapack_, dgetrf, (m, n, a, lda, ipiv, info));
fpk_serv_set_num_threads_local(old_threads);
}
...
} |
Thankyou @Alexsandruss for your response.
Thanks! |
@ajay-fuji is this still a pressing issue? |
I still want to understand reason behind setting local threads to 1 in one case ( |
@ajay-fuji Sorry for answering this almost a year later: It looks like to me that in cases that routines are already multithreaded, they want to limit the number of threads taken by the blas/lapack calls to match the thread that called it. An example is: in svd there is |
Hi,
In the mkl function call, I have seen two types of call of same basic function, prefixed with
x
andxx
.e.g,xsyrk
andxxsyrk
.What is difference between these two type of functions and how is it different from function implementation in netlib LAPACK or OpenBLAS.
The text was updated successfully, but these errors were encountered: