Execute all non-unsafe opcodes on calling thread

This will require more testing of course, but I think it should be safe.
This would increase the potential maximal throughput in group hosts
significantly.
This commit is contained in:
Robbert van der Helm
2020-10-27 23:18:59 +01:00
parent eb8d4ae1d8
commit fac820c25a
2 changed files with 7 additions and 15 deletions
-3
View File
@@ -137,9 +137,6 @@ win32_thread_trampoline(fu2::unique_function<void()>* entry_point);
* `CreateThread()`, some thread local information does not get initialized
* which can lead to memory errors.
*
* TODO: Once these changes are complete, check if we can drop `PluginContext`
* again and execute all 'safe' opcodes on the calling thread.
*
* @note This should be used instead of `std::thread` or `std::jthread` whenever
* the thread directly calls third party library code, i.e. `LoadLibrary()`,
* `FreeLibrary()`, the plugin's entry point, or any of the `AEffect::*()`