switch to TMVars for thread safety when using the async extension
TVars were not updated atomically, which was ok when each thread got its own External that was the only thing using these TVars. But, with the async extension, several External instances can share the same var, so it needs to be a TMVar to avoid read/write conflicts. In particular, this makes PREPARE only be sent once.
This commit is contained in:
parent
7da2d4dd2d
commit
198b709561
4 changed files with 37 additions and 35 deletions
|
@ -87,7 +87,7 @@ An example of sending multiple replies to a request is `LISTCONFIGS`, eg:
|
|||
|
||||
## notes
|
||||
|
||||
There will generally be one job for each thread that git-annex runs
|
||||
There will be one job number for each thread that git-annex runs
|
||||
concurrently, so around the same number as the -J value, although in some
|
||||
cases git-annex does more concurrent operations than the -J value.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue