[FEA] Unify API layers and remove the `mg` namespace
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
Is your feature request related to a problem? Please describe.
The unification of API layers and the removal of the mg namespace would simply the API and make it easier for new users to deploy cuVS in their projects.
Describe the solution you'd like
Instead of using the mg namespace, users would initialize a NCCL clique and set it on a resource handler. The user would make a generic call to the API and the resource handler would then inform cuVS on the appropriate algorithm implementation to run. For instance, if the resource handler contains a NCCL clique, it would run the MG implementation of the algorithm.
This change requires a modification of the entry functions called by the API. These would now be in charge of checking the presence of a NCCL clique on the resource handler and dispatch appropriately.
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 no files or tests. Start by locating the API entry functions and resource-handler types involved in NCCL clique handling, then trace how the MG implementation is selected. Done means generic API calls dispatch through the resource handler without requiring an mg namespace.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100