oneapi-src / oneapi-src/ishmem
Split host and device libraries
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
This is a feature request.
Linking libishmem.a is very slow due to device code compilation/linking.
I only intended to use the host side features.
NVSHMEM provides libnvshmem_host.so and nvshmemx_hostlib_init_attr/nvshmemx_hostlib_finalize APIs.
I'd like Intel SHMEM to match that.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names libishmem.a, libnvshmem_host.so, and the nvshmemx_hostlib_init_attr/nvshmemx_hostlib_finalize APIs, but no repository files or tests. Start by locating the library build configuration and existing host/device initialization entry points. Done means host-only users can link a separate host library without device compilation and have the requested host lifecycle APIs.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100