README 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158
  1. ++=================++
  2. || I. Introduction ||
  3. ++=================++
  4. +---------------------
  5. | I.a. What is StarPU?
  6. StarPU is a runtime system that offers support for heterogeneous multicore
  7. machines. While many efforts are devoted to design efficient computation kernels
  8. for those architectures (e.g. to implement BLAS kernels on GPUs or on Cell's
  9. SPUs), StarPU not only takes care of offloading such kernels (and implementing
  10. data coherency across the machine), but it also makes sure the kernels are
  11. executed as efficiently as possible.
  12. +------------------------
  13. | I.b. What StarPU is not
  14. StarPU is not a new language, and it does not extends existing languages either.
  15. StarPU does not help to write computation kernels.
  16. +---------------------------------
  17. | I.c. (How) Could StarPU help me?
  18. While StarPU will not make it easier to write computation kernels, it does
  19. simplify their actual offloading as StarPU handle most low level aspects
  20. transparently.
  21. Obviously, it is crucial to have efficient kernels, but it must be noted that
  22. the way those kernels are mapped and scheduled onto the computational resources
  23. also affect the overall performance to a great extent.
  24. StarPU is especially helpful when considering multiple heterogeneous processing
  25. resources: statically mapping and synchronizing tasks in such a heterogeneous
  26. environment is already very difficult, making it in a portable way is virtually
  27. impossible. On the other hand, the scheduling capabilities of StarPU makes it
  28. possible to easily exploit all processors at the same time while taking
  29. advantage of their specificities in a portable fashion.
  30. ++==================++
  31. || II. Requirements ||
  32. ++==================++
  33. * make
  34. * gcc (version >= 4.1)
  35. * if CUDA support is enabled
  36. * CUDA (version >= 2.2)
  37. * CUBLAS (version >= 2.2)
  38. * if OpenCL support is enabled
  39. * AMD SDK >= 2.3 if AMD driver is used
  40. * CUDA >= 3.2 if NVIDIA driver is used
  41. * extra requirements for the svn version (we usually use the Debian testing
  42. versions)
  43. * autoconf (version >= 2.60)
  44. * automake
  45. * makeinfo
  46. * Remark: It is strongly recommanded that you also install the hwloc library
  47. before installing StarPU. This permits StarPU to actually map the processing
  48. units according to the machine topology. For more details on hwloc, see
  49. http://www.open-mpi.org/projects/hwloc/ .
  50. ++=====================++
  51. || III. Getting StarPU ||
  52. ++=====================++
  53. StarPU is available on https://gforge.inria.fr/projects/starpu/.
  54. The project's SVN repository can be checked out through anonymous
  55. access with the following command(s).
  56. $ svn checkout svn://scm.gforge.inria.fr/svn/starpu/trunk
  57. $ svn checkout --username anonsvn https://scm.gforge.inria.fr/svn/starpu/trunk
  58. The password is 'anonsvn'
  59. ++=============================++
  60. || IV. Building and Installing ||
  61. ++=============================++
  62. +---------------------------
  63. | IV.a. For svn version only
  64. $ ./autogen.sh
  65. +-----------------------
  66. | IV.b. For all versions
  67. $ ./configure
  68. $ make
  69. $ make install
  70. +---------------------
  71. | IV.c. Windows build:
  72. StarPU can be built using MinGW or Cygwin. To avoid the cygwin dependency,
  73. we provide MinGW-built binaries. The build process produces libstarpu.dll,
  74. libstarpu.def, and libstarpu.lib, which should be enough to use it from e.g.
  75. Microsoft Visual Studio.
  76. A few details need to be fixed when building StarPU on windows:
  77. - To get a .def file built, make sure that MSVC's lib.exe tool is in PATH.
  78. - Update the video drivers to the latest stable release available for your
  79. hardware. Older ATI drivers (< 2.3) contain bugs that cause OpenCL support in
  80. StarPU to hang or exhibit incorrect behaviour.
  81. - c:\cuda\include\host_defines.h has a bogus CUDARTAPI definition which makes
  82. linking fail completely. Replace the first occurence of
  83. #define CUDARTAPI
  84. with
  85. #ifdef _WIN32
  86. #define CUDARTAPI __stdcall
  87. #else
  88. #define CUDARTAPI
  89. #endif
  90. While at it, you can also comment the __cdecl definition to avoid spurious
  91. warnings.
  92. - If you have a non-english version of windows, use
  93. export LANG=C
  94. else libtool has troubles parsing the translated output of the toolchain.
  95. - libtool is not able to find the libraries automatically, you need to make some
  96. copies:
  97. copy c:\cuda\lib\cuda.lib c:\cuda\lib\libcuda.lib
  98. copy c:\cuda\lib\cudart.lib c:\cuda\lib\libcudart.lib
  99. copy c:\cuda\lib\cublas.lib c:\cuda\lib\libcublas.lib
  100. copy c:\cuda\lib\cufft.lib c:\cuda\lib\libcufft.lib
  101. copy c:\cuda\lib\OpenCL.lib c:\cuda\lib\libOpenCL.lib
  102. ++===========++
  103. || V. Trying ||
  104. ++===========++
  105. Some examples ready to run are installed into $prefix/lib/starpu/{examples,mpi}
  106. ++=============++
  107. || VI. Upgrade ||
  108. ++=============++
  109. To upgrade your source code from older version (there were quite a few
  110. renamings), use the tools/rename.sh script
  111. ++==============++
  112. || VII. Contact ||
  113. ++==============++
  114. For any questions regarding StarPU, please contact the starpu-devel
  115. mailing-list at starpu-devel@lists.gforge.inria.fr .