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
With change #220 we are fixing host buffer ownership issues by always creating copy of the host buffer. We can avoid doing so depending on the PJRT_HostBufferSemantics given to us by PJRT API caller. For example when semantic is PJRT_HostBufferSemantics_kImmutableUntilTransferCompletes we can just use the given host buffer and call done_with_host_buffer.ready() after executing in runtime.
The text was updated successfully, but these errors were encountered:
With change #220 we are fixing host buffer ownership issues by always creating copy of the host buffer. We can avoid doing so depending on the
PJRT_HostBufferSemantics
given to us by PJRT API caller. For example when semantic isPJRT_HostBufferSemantics_kImmutableUntilTransferCompletes
we can just use the given host buffer and calldone_with_host_buffer.ready()
after executing in runtime.The text was updated successfully, but these errors were encountered: