A subset of LAPACK routines redesigned for heterogenous computing
The ScaLAPACK (or Scalable LAPACK) library includes a subset of LAPACK routines redesigned for distributed memory MIMD parallel computers. It is currently written in a Single-Program-Multiple-Data style using explicit message passing for interprocessor communication. It assumes matrices are laid out in a two-dimensional block cyclic decomposition.
ScaLAPACK is designed for heterogeneous computing and is portable on any computer that supports MPI or PVM.
Like LAPACK, the ScaLAPACK routines are based on block-partitioned algorithms in order to minimize the frequency of data movement between different levels of the memory hierarchy. (For such machines, the memory hierarchy includes the off-processor memory of other processors, in addition to the hierarchy of registers, cache, and local memory on each processor.) The fundamental building blocks of the ScaLAPACK library are distributed memory versions (PBLAS) of the Level 1, 2 and 3 BLAS, and a set of Basic Linear Algebra Communication Subprograms (BLACS) for communication tasks that arise frequently in parallel linear algebra computations. In the ScaLAPACK routines, all interprocessor communication occurs within the PBLAS and the BLACS. One of the design goals of ScaLAPACK was to have the ScaLAPACK routines resemble their LAPACK equivalents as much as possible.
- Developed at science
- Sources inherited from project openSUSE:Factory
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:Rebuild/scalapack && cd $_
- Create Badge
Source Files
Filename | Size | Changed |
---|---|---|
_multibuild | 0000000161 161 Bytes | |
scalapack-2.0.2-shared-blacs.patch | 0000000878 878 Bytes | |
scalapack-2.0.2-shared-lib.patch | 0000001756 1.71 KB | |
scalapack-2.0.2.tgz | 0004779534 4.56 MB | |
scalapack.changes | 0000002913 2.84 KB | |
scalapack.spec | 0000015244 14.9 KB |
Revision 4 (latest revision is 26)
- Add magic to limit the number of flavors built in the in the OBS ring. - Make sure the Factory validator gets %pname as package name. - Convert to multibuild - Add HPC build using environment modules (FATE#321715). - Generate baselib.conf dynamically and only for the non-HPC builds: this avoids issues with the source validator.
Comments 0