Thank you very much for your help.
Stan Tomov wrote:Jpeinado,
We leave it up to the user to allocate memory, e.g., working spaces, etc.; the magma and magmablas libraries do not need and do not allocate additional memory space.
OK. Really I dont know what is happening, but when compiling with -lmagmablas option my mexfiles, then MATLAB crash. This crash happens even if I dont include any MAGMA call when running the mex. It is really strange...
Stan Tomov wrote: The examples in the testing directory use pinned memory for performance, but non-pinned would work as well.
Stan Tomov wrote: Can you run other CUDA-based routines/code (not just a single CUDA kernel) through matlab?
Yes. In my mex code I call several CUBLAS routines (perhaps, all of them are kernels? ) and then work OK. Even I tested/tried a commercial CUDA LAPACK called CULATOOLS, and also it worked. I dont like these commercial histories, and I prefer MAGMA (I have always been using BLAS, LAPACK, SCALAPACK free (or MKL) versions before, in my work, phD...etc). Moreover, at this time, the performance of sgesv CULATOOLS it is not very good, but it works, really works OK.
Stan Tomov wrote:We are still working on releasing the sources. I can send you some if you think that may be helpful.
Good to hear this!!
Thank you for your offering. Anyway I would like to know if it is possible to get the sgesv source code, but the problem is that I dont know if this routine relies on your magmablas package. Does it need the magmablas library?, or can it be used with CUBLAS?
Again, thank you very much for your interest