-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[fix] Fix MoE workspace info by storing Torch tensor itself instead of data_ptr #5900
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[fix] Fix MoE workspace info by storing Torch tensor itself instead of data_ptr #5900
Conversation
…f data_ptr Signed-off-by: Jinyang Yuan <154768711+jinyangyuan-nvidia@users.noreply.github.com>
|
/bot run |
|
PR_Github #11504 [ run ] triggered by Bot |
|
PR_Github #11504 [ run ] completed with state |
|
/bot run |
|
PR_Github #11510 [ run ] triggered by Bot |
|
PR_Github #11510 [ run ] completed with state |
|
/bot run |
|
PR_Github #11529 [ run ] triggered by Bot |
|
PR_Github #11529 [ run ] completed with state |
…f data_ptr (NVIDIA#5900) Signed-off-by: Jinyang Yuan <154768711+jinyangyuan-nvidia@users.noreply.github.com> Signed-off-by: Yuxin <yuxinz@nvidia.com>
The GPU memory allocated for MoE workspace may be reallocated for other tensors because the workspace info stores data_ptr instead of Torch tensor itself. This PR fixes this potential issue.