Skip to content

Commit

Permalink
remove warning about encryption on cuda tensors
Browse files Browse the repository at this point in the history
  • Loading branch information
bchess committed Apr 30, 2024
1 parent 985f80d commit 3a139c0
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/subprocess-serialization.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Presuming your tensors are in CUDA memory, there are a couple different options.
### Option 1: Communicate the CUDA tensors directly
CUDA tensors can be "shared" to a subprocess very efficiently since it's only communicating a pointer to device memory.

Basically send the CUDA tensors over a `multiprocessing.Queue` to a subprocess that does the serialization. Ensure that the CUDA tensors remain **unmodified** in device memory until the serialization process finishes. Note if using encryption, the tensors may be encrypted-in-place so they must also not read again until serialization finishes.
Basically send the CUDA tensors over a `multiprocessing.Queue` to a subprocess that does the serialization. Ensure that the CUDA tensors remain **unmodified** in device memory until the serialization process finishes.

```python
import torch
Expand Down

0 comments on commit 3a139c0

Please sign in to comment.