[XPU] [DeepNVMe] use same cpu_op_desc_t with cuda #6645
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Liangliang-Ma
requested review from
loadams,
tjruwase,
jomayeri and
awan-10
as code owners
tjruwase
approved these changes
Oct 21, 2024
|
@tjruwase Could you please help to re-trigger the checks for xpu-max1100 workflow updation#6646 ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have found that #6592 uses
_pinned_tensor_mgrto create cpu bounce buffer, which is same with what our xpu accelerator currently doing.So no need to use xpu device specific cpu_op_desc_t.
In this PR:
This issue cannot be easily done with revert #6532 , for we added some source file as last time GDS feature going in DS. So file this new PR :)