Skip to content
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

[TransferEngine] Support Status return value #125

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

yuan-luo
Copy link
Contributor

This PR implements Status return value in the TransferEngine.
This is for better debugging and is able to avoid cross-module error code conflict.

@yuan-luo
Copy link
Contributor Author

This PR is to replace #118.

@yuan-luo yuan-luo force-pushed the support_status_prod branch from d2d4f9d to 4beb1ee Compare February 28, 2025 15:47
Copy link
Collaborator

@doujiang24 doujiang24 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this the continue part of #118 , we'd better use push new commits in 118, instead of open a new PR. Or, close 118 could be better too.

@@ -57,6 +57,31 @@ int TransferEngine::freeEngine() {
return 0;
}

int TransferEngine::submitTransfer(BatchID batch_id,
const std::vector<TransferRequest> &entries) {
// TODO: return Status in public function.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you explain the plan to reach it? seems we just use Status in internal APIs?

Copy link
Contributor Author

@yuan-luo yuan-luo Mar 3, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The plan is to replace the return value in the public functions, so as the return values will not conflict with each other between cross components. The reason to set TODO here is because the complete converting work is non-trivial, which may impact the vLLM adapter in the Mooncake upstream. So I send out this PR to collect some review comments.

Were this approach approved, I'd like to change all the external APIs' return value into Status.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, that make sense, the exposed C APIs need to take care too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, I'll proceed with this PR.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@doujiang24 Please take another look at this PR. Thanks.

@yuan-luo yuan-luo force-pushed the support_status_prod branch 2 times, most recently from 8e29625 to 5df40a7 Compare March 5, 2025 14:47
@yuan-luo yuan-luo force-pushed the support_status_prod branch from 5df40a7 to b9733af Compare March 5, 2025 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants