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
Certain parts of pyctr could probably benefit from threading support. One idea I have is to split file reading and de/encryption into two threads with their own locks; since this is mostly IO-bound it should be fine with the GIL (and pycryptodome releases the GIL when doing crypto work).
Per file:
Lock file-reading thread
Read from file (CIA, NCCH, etc.)
Unlock file-reading thread
Pass to decrypt thread
Lock decrypt thread
Decrypt data
Unlock decrypt thread
Return data to main thread
This would allow a file read operation to continue at the same time decryption is happening for another part of the file.
Certain parts of pyctr could probably benefit from threading support. One idea I have is to split file reading and de/encryption into two threads with their own locks; since this is mostly IO-bound it should be fine with the GIL (and pycryptodome releases the GIL when doing crypto work).
Per file:
This would allow a file read operation to continue at the same time decryption is happening for another part of the file.
(connected to: ihaveamac/ninfs#94)
The text was updated successfully, but these errors were encountered: