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

Amend memory hierarchy for kp::Operations so they can be created separately #160

Closed
axsaucedo opened this issue Feb 21, 2021 · 0 comments · Fixed by #164
Closed

Amend memory hierarchy for kp::Operations so they can be created separately #160

axsaucedo opened this issue Feb 21, 2021 · 0 comments · Fixed by #164

Comments

@axsaucedo
Copy link
Member

Currently kp::Operations own commandbuffers which makes them dependent to sequences on the memory hierarchy, however from further assessment this can be removed such that the commandbuffer is only passed for recording commands. This would allow kp::Operation memory to be managed by the top level kp::Manager which then would enable for kp::Operations to be created dynamically and initialised separate to Sequences, Managers and Tensors. This would allow also for much more dynamic interaction with these objectsi in the Python bindings.

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