You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
|
|
3 weeks ago | |
|---|---|---|
| .. | ||
| Makefile | 3 weeks ago | |
| README.md | 3 weeks ago | |
| psb_spmv_overlap_sbatch.sh | 4 weeks ago | |
| psb_spmv_test.f90 | 3 weeks ago | |
README.md
spmv overlap communication test
This test was added after introducing different communication schemes in PSBLAS.
It exercises the overlapped SpMV communication path inside psb_spmm.
Communication pattern:
- split exchange/computation flow (
start+ local compute +wait) - halo/overlap update through internal swap routines used by SpMV kernels
- same matrix/vector workload repeated across schemes for timing comparison
Communication schemes compared:
psb_comm_isend_irecv_psb_comm_ineighbor_alltoallv_psb_comm_persistent_ineighbor_alltoallv_
Unlike swapdata/, which checks direct halo exchange, this test covers the
overlapped SpMV workflow.
Run options
- Default PDE-generated matrix:
./runs/psb_spmv_kernel [--gpu=TRUE|FALSE] [--nooverlap] - External matrix:
./runs/psb_spmv_kernel [--gpu=TRUE|FALSE] --matrix=<path> [--fmt=MM|HB] [--nooverlap]
The overlap path is enabled by default; pass --nooverlap to force the non-overlapped halo-update path.
When --matrix is provided, the benchmark reads and distributes that matrix instead of generating the 3D PDE test matrix.