README 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194
  1. # StarPU --- Runtime system for heterogeneous multicore architectures.
  2. #
  3. # Copyright (C) 2009-2021 Université de Bordeaux, CNRS (LaBRI UMR 5800), Inria
  4. #
  5. # StarPU is free software; you can redistribute it and/or modify
  6. # it under the terms of the GNU Lesser General Public License as published by
  7. # the Free Software Foundation; either version 2.1 of the License, or (at
  8. # your option) any later version.
  9. #
  10. # StarPU is distributed in the hope that it will be useful, but
  11. # WITHOUT ANY WARRANTY; without even the implied warranty of
  12. # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
  13. #
  14. # See the GNU Lesser General Public License in COPYING.LGPL for more details.
  15. #
  16. ++=================++
  17. || I. Introduction ||
  18. ++=================++
  19. +---------------------
  20. | I.a. What is StarPU?
  21. StarPU is a runtime system that offers support for heterogeneous multicore
  22. machines. While many efforts are devoted to design efficient computation kernels
  23. for those architectures (e.g. to implement BLAS kernels on GPUs),
  24. StarPU not only takes care of offloading such kernels (and
  25. implementing data coherency across the machine), but it also makes
  26. sure the kernels are executed as efficiently as possible.
  27. +------------------------
  28. | I.b. What StarPU is not
  29. StarPU is not a new language, and it does not extend existing languages either.
  30. StarPU does not help to write computation kernels.
  31. +---------------------------------
  32. | I.c. (How) Could StarPU help me?
  33. While StarPU will not make it easier to write computation kernels, it does
  34. simplify their actual offloading as StarPU handle most low level aspects
  35. transparently.
  36. Obviously, it is crucial to have efficient kernels, but it must be noted that
  37. the way those kernels are mapped and scheduled onto the computational resources
  38. also affect the overall performance to a great extent.
  39. StarPU is especially helpful when considering multiple heterogeneous processing
  40. resources: statically mapping and synchronizing tasks in such a heterogeneous
  41. environment is already very difficult, making it in a portable way is virtually
  42. impossible. On the other hand, the scheduling capabilities of StarPU makes it
  43. possible to easily exploit all processors at the same time while taking
  44. advantage of their specificities in a portable fashion.
  45. ++==================++
  46. || II. Requirements ||
  47. ++==================++
  48. * make
  49. * gcc (version >= 4.1)
  50. * if CUDA support is enabled
  51. * CUDA (version >= 2.2)
  52. * CUBLAS (version >= 2.2)
  53. * if OpenCL support is enabled
  54. * AMD SDK >= 2.3 if AMD driver is used
  55. * CUDA >= 3.2 if NVIDIA driver is used
  56. * extra requirements for the svn version (we usually use the Debian testing
  57. versions)
  58. * autoconf (version >= 2.60)
  59. * automake
  60. * makeinfo
  61. * libtool (version >= 2)
  62. * Remark: It is strongly recommanded that you also install the hwloc library
  63. before installing StarPU. This permits StarPU to actually map the processing
  64. units according to the machine topology. For more details on hwloc, see
  65. http://www.open-mpi.org/projects/hwloc/ .
  66. * To build the StarPU-Top tool the following packages (along with
  67. their development files) are also required:
  68. * libqt4-dev >= 4.7
  69. * libqt4-network
  70. * libqt4-opengl
  71. * libqt4-sql
  72. * qt4-qmake
  73. ++=====================++
  74. || III. Getting StarPU ||
  75. ++=====================++
  76. StarPU is available on https://gitlab.inria.fr/starpu/starpu
  77. The GIT repository access can be checked out with the following command.
  78. $ git clone git@gitlab.inria.fr:starpu/starpu.git
  79. ++=============================++
  80. || IV. Building and Installing ||
  81. ++=============================++
  82. +---------------------------
  83. | IV.a. For svn version only
  84. Please skip this step if you are building from a tarball.
  85. $ ./autogen.sh
  86. +-----------------------
  87. | IV.b. For all versions
  88. $ ./configure
  89. $ make
  90. $ make install
  91. +---------------------
  92. | IV.c. Windows build:
  93. StarPU can be built using MinGW or Cygwin. To avoid the cygwin dependency,
  94. we provide MinGW-built binaries. The build process produces libstarpu.dll,
  95. libstarpu.def, and libstarpu.lib, which should be enough to use it from e.g.
  96. Microsoft Visual Studio.
  97. Update the video drivers to the latest stable release available for your
  98. hardware. Old ATI drivers (< 2.3) contain bugs that cause OpenCL support in
  99. StarPU to hang or exhibit incorrect behaviour.
  100. For details on the Windows build process, see the INSTALL file.
  101. ++======================================================++
  102. || V. Running StarPU Applications on Microsoft Visual C ||
  103. ++======================================================++
  104. Batch files are provided to run StarPU applications under Microsoft
  105. Visual C. They are installed in path_to_starpu/bin/msvc.
  106. To execute a StarPU application, you first need to set the environment
  107. variable STARPU_PATH.
  108. c:\....> cd c:\cygwin\home\ci\starpu\
  109. c:\....> set STARPU_PATH=c:\cygwin\home\ci\starpu\
  110. c:\....> cd bin\msvc
  111. c:\....> starpu_open.bat starpu_simple.c
  112. The batch script will run Microsoft Visual C with a basic project file
  113. to run the given application.
  114. The batch script starpu_clean.bat can be used to delete all
  115. compilation generated files.
  116. The batch script starpu_exec.bat can be used to compile and execute a
  117. StarPU application from the command prompt.
  118. c:\....> cd c:\cygwin\home\ci\starpu\
  119. c:\....> set STARPU_PATH=c:\cygwin\home\ci\starpu\
  120. c:\....> cd bin\msvc
  121. c:\....> starpu_exec.bat ..\..\..\..\examples\basic_examples\hello_world.c
  122. MSVC StarPU Execution
  123. ...
  124. /out:hello_world.exe
  125. ...
  126. Hello world (params = {1, 2.00000})
  127. Callback function got argument 0000042
  128. c:\....>
  129. ++===================++
  130. || VI. Documentation ||
  131. ++===================++
  132. Doxygen documentation is available in doc/doxygen. If the doxygen
  133. tools are available on the machine, pdf and html documentation can be
  134. generated by running
  135. $ make -C doc
  136. ++=============++
  137. || VII. Trying ||
  138. ++=============++
  139. Some examples ready to run are installed into $prefix/lib/starpu/{examples,mpi}
  140. ++===============++
  141. || VIII. Upgrade ||
  142. ++===============++
  143. To upgrade your source code from older version (there were quite a few
  144. renamings), use the tools/dev/rename.sh script
  145. ++=============++
  146. || IX. Contact ||
  147. ++=============++
  148. For any questions regarding StarPU, please contact the starpu-devel
  149. mailing-list at starpu-devel@inria.fr.