udiskslinuxprovider: Move udev monitor in a separate thread #1221
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Traditionally the master uevent monitor was bound to a main thread. However with most of the D-Bus object machinery, interface updates, etc. being done in the same thread, lost uevents were spotted on resource-constrained systems.
Better to dedicate a new thread for incoming uevents that are sent to a probing thread right away, effectively acting as a storage queue.
Fixes #1133