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

[FEA] make_tma_copy doesnot support shared-to-shared copy #1657

Open
ziyuhuang123 opened this issue Jul 27, 2024 · 3 comments
Open

[FEA] make_tma_copy doesnot support shared-to-shared copy #1657

ziyuhuang123 opened this issue Jul 27, 2024 · 3 comments

Comments

@ziyuhuang123
Copy link

Describe the bug
In PTX, I noticed that

cp.async.bulk.dst.src.completion_mechanism [dstMem], [srcMem], size, [mbar]

.dst =                  { .shared::cluster }
.src =                  { .shared::cta }
.completion_mechanism = { .mbarrier::complete_tx::bytes }

supports shared-to-shared copy. But in cute, make_tma_copy has to be global to shared. Why? Could you modify it?

@ziyuhuang123 ziyuhuang123 added ? - Needs Triage bug Something isn't working labels Jul 27, 2024
@thakkarV
Copy link
Collaborator

thakkarV commented Jul 27, 2024

This is not a bug. We have not needed smem to smem TMA copies. Do you have a specific need for this?

@mnicely mnicely changed the title [BUG]make_tma_copy doesnot support shared-to-shared copy [FEA] make_tma_copy doesnot support shared-to-shared copy Jul 27, 2024
@mnicely mnicely added feature request New feature or request and removed bug Something isn't working ? - Needs Triage labels Jul 27, 2024
Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

Copy link

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants