5 posts
• Page **1** of **1**

I'm interested in performing QR and Cholesky matrix factorization on multiple GPUs. I am able to perform these factorizations on a single GPU using the MATLAB 2013b Parallel Computing Toolbox via the qr and chol functions. Are there instructions for invoking the QR and Cholesky MAGMA routines from within MATLAB so that multiple GPUs can be exploited? Why doesn't MATLAB use MAGMA for its GPU matrix factorization library so that multiple GPUs can be exploited?

- stumarcus
**Posts:**2**Joined:**Fri Mar 07, 2014 5:28 pm

To my knowledge, Matlab does not currently support multi-GPU functions, but that is a question/suggestion for MathWorks.

-mark

-mark

- mgates3
**Posts:**442**Joined:**Fri Jan 06, 2012 2:13 pm

How difficult is it to invoke the MAGMA routines from within a MATLAB program? Are there instructions for doing this?

- stumarcus
**Posts:**2**Joined:**Fri Mar 07, 2014 5:28 pm

I wrote a tutorial on matlab+cuda using mex files a few years ago:

http://faculty.washington.edu/dushaw/ep ... l_2_10.pdf

A little dated, but I think it is still valid, generally.

Matlab's parallel processing toolbox has mostly superseded my laborious mex files, however. But it is nice to have the mex file approach working, just in case.

Also, matlab may have its own cuda libraries internally. One issue that has come up is a user's mex file may try to use these libraries first, rather than the expected libraries from cuda. One can test which libraries are used by doing >> !ldd usersmexfile.mex from within matlab. Perhaps matlab has sorted this issue out by now, however. (assuming linux as the OS here)

http://faculty.washington.edu/dushaw/ep ... l_2_10.pdf

A little dated, but I think it is still valid, generally.

Matlab's parallel processing toolbox has mostly superseded my laborious mex files, however. But it is nice to have the mex file approach working, just in case.

Also, matlab may have its own cuda libraries internally. One issue that has come up is a user's mex file may try to use these libraries first, rather than the expected libraries from cuda. One can test which libraries are used by doing >> !ldd usersmexfile.mex from within matlab. Perhaps matlab has sorted this issue out by now, however. (assuming linux as the OS here)

- Boxed Cylon
**Posts:**27**Joined:**Sat Nov 21, 2009 6:03 pm

5 posts
• Page **1** of **1**

Users browsing this forum: Bing [Bot] and 2 guests