You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: