[Enhancement] Provide a clearer explanation of RC-to-DC adapter behavior
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 9
- Forks
- 1
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Ask: Several storage partners now have been asking for clarify around the RC-to-DC adapter functionality, since cuObject v1.2.0 uses DC (only), so a stock libcuobjserver cannot serve it without an RC-to-DC adapter.
We have a solution from versity in https://github.com/versity/versitygw/tree/main/cuwrapper but in our code & docs this needs further elaboration.
Contributor guide
No contributing guide indexed for this repository
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
Start by reading the issue and the referenced versity cuwrapper implementation, then locate the existing RC-to-DC adapter code and documentation in hipObject. Done means the repository clearly explains the adapter behavior, why cuObject v1.2.0 requires it, and how libcuobjserver users should account for it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100