-
Notifications
You must be signed in to change notification settings - Fork 98
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
Add issue_token
attribute to IpuDmaMemcpyNdOp
#1209
Conversation
I'm curious - when do you want to do this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The test fails are flakes (something about caching the ccache dir) |
If you have a sequence of bd writes using the same bd_id, to avoid overwriting a bd before fully executed. |
Makes sense |
@makslevental Could you help with approving the workflow again? |
Sure but I pinged you on slack about a longer-term solution... |
e1e2aa8
to
f82e475
Compare
addressed with updated doc
0f8b591
to
22289fc
Compare
This PR adds an
issue_token
field toIpuDmaMemcpyNdOp
. This allows more fine-grained control of which DMA operations should issue tokens and enables synchronization on MM2S DMA operations in addition to the S2MM DMA operations which were implicitly enabled earlier. The newissue_token
field is set tofalse
by default for backward compatibility with the implicit issuance of tokens for S2MM DMA operations only.cc @fifield @jgmelber @AndraBisca Could you help review?