[Core] Add VRAM_SEG support for NIXL OBJ plugin#2640
Conversation
Summary of ChangesHello @jgoldsch12, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces crucial support for VRAM_SEG memory types within the NIXL OBJ storage backend. The primary goal is to allow users to specify 'cuda' as a Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces VRAM_SEG support for the NIXL OBJ backend. This is achieved by updating validate_nixl_backend to permit 'cuda' devices with the 'OBJ' backend for both dynamic and static storage configurations. Additionally, init_mem_handlers is modified to register memory in page-sized chunks, which prevents exceeding the maximum buffer size of the underlying NIXL plugin. This change aligns memory registration with the existing transfer descriptor creation logic.
6bb78aa to
585dea9
Compare
|
@vvenkates27 who could be another approver for this PR? |
|
Signed-off-by: Jason Goldschmidt <jason.goldschmidt@dell.com>
585dea9 to
91b930c
Compare
Add VRAM_SEG support for NIXL OBJ plugin Signed-off-by: Jason Goldschmidt <jason.goldschmidt@dell.com>
Add VRAM_SEG support for NIXL OBJ plugin Signed-off-by: Jason Goldschmidt <jason.goldschmidt@dell.com> Signed-off-by: Aaron Wu <aaron.wu@dell.com>
Add VRAM_SEG support for NIXL OBJ plugin Signed-off-by: Jason Goldschmidt <jason.goldschmidt@dell.com>
Add VRAM_SEG support for NIXL OBJ plugin Signed-off-by: Jason Goldschmidt <jason.goldschmidt@dell.com>
Add VRAM_SEG support for NIXL OBJ plugin Signed-off-by: Jason Goldschmidt <jason.goldschmidt@dell.com>
Add VRAM_SEG support for NIXL OBJ plugin Signed-off-by: Jason Goldschmidt <jason.goldschmidt@dell.com>
Add VRAM_SEG support for NIXL OBJ plugin Signed-off-by: Jason Goldschmidt <jason.goldschmidt@dell.com>
This commit introduces VRAM_SEG support for the NIXL OBJ backend. With the introduction of "accelerated" engines for the NIXL OBJ backend, the VRAM_SEG memory type can now be supported and should not be rejected by the LMCache NIXL storage backend. This allows a user to specify a 'nixl_device_buffer' of type 'cuda' in the LMCache configuration. Previously, this type would fail when used with the OBJ nixl backend.
Signed-off-by: Jason Goldschmidt jason.goldschmidt@dell.com