Packages / Fedora 44 / Unspecified / scalapack-common
Package: scalapack-common
External Resources:
Homepage: [www.netlib.org]
Similar packages:
- [scalapack-mpich]
ScaLAPACK libraries compiled against mpich
- [scalapack-mpich-devel]
Development libraries for ScaLAPACK (mpich)
- [scalapack-mpich-static]
Static libraries for ScaLAPACK (mpich)
- [scalapack-openmpi]
ScaLAPACK libraries compiled against openmpi
- [scalapack-openmpi-devel]
Development libraries for ScaLAPACK (openmpi)
- [scalapack-openmpi-static]
Static libraries for ScaLAPACK (openmpi)
Common files for scalapack
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 inter-processor 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 inter-processor 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.
This package contains common files which are not specific
to any MPI implementation.
No published records match this suite and architecture filter.
Package file paths (9)
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
- /usr/include/blacs
- /usr/include/blacs/Bdef.h
- /usr/lib64/cmake/scalapack-2.2.2
- /usr/lib64/cmake/scalapack-2.2.2/scalapack-config.cmake
- /usr/lib64/cmake/scalapack-2.2.2/scalapack-config-version.cmake
- /usr/lib64/cmake/scalapack-2.2.2/scalapack-targets.cmake
- /usr/lib64/cmake/scalapack-2.2.2/scalapack-targets-noconfig.cmake
- /usr/share/doc/scalapack-common
- /usr/share/doc/scalapack-common/README