-
```
software rendering depends on CPU power, most architectures are going
multi-core
it would be a good idea to add some basic threading support to pixeltoaster
so this CPU power can be accessed in a…
-
```
software rendering depends on CPU power, most architectures are going
multi-core
it would be a good idea to add some basic threading support to pixeltoaster
so this CPU power can be accessed in a…
-
Mutexes are in theory twice as expensive as an atomic coroutine's operation, as a mutex itself must internally apply an atomic operation to lock and another to unlock.
We should be able to kill mutex…
-
```
software rendering depends on CPU power, most architectures are going
multi-core
it would be a good idea to add some basic threading support to pixeltoaster
so this CPU power can be accessed in a…
-
### Is your feature request related to a problem?
The pthread implementation of condition variables and mutexes uses only `std::chrono::system_clock` which is non monotonic.
CPP reference recomm…
-
- By default, named synchronization objects (mutexes, semaphores, and events) are usable by multiple users. This could be problematic on systems where untrusted users may run code.
- It would be usef…
-
The following test is failing, it looks like named mutexes used cross-process are not working:
https://github.com/dotnet/runtime/blob/14835fbb7fdb2065983866ac186ed8408ee9b388/src/libraries/System.Thr…
-
```
software rendering depends on CPU power, most architectures are going
multi-core
it would be a good idea to add some basic threading support to pixeltoaster
so this CPU power can be accessed in a…
-
In rust-secp256k1 we're exploring how we can best support a signing API for systems which potentially have no allocator, may be operating multiple threads, but which have very limited threading primit…
-
Hi @davehorton
We are using `mod_audio_fork` module. I was going through the code and could not understand the need to acquire/lock multiple mutexes in func `fork_frame()`
1. mutex part of variable…