test: mt: introduce a mtt-framework-provided semaphores #1050
Conversation
These semaphores are dedicated to interprocess synchronization between the parent and the child processes.
There was a problem hiding this comment.
Reviewed 10 of 10 files at r1.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on @janekmi)
There was a problem hiding this comment.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @janekmi)
tests/multithreaded/common/mtt.c, line 71 at r1 (raw file):
/* * XXX use sem_close() in a for-loop */
sem_unlink() has to be used here too (with the appropriate name of the semaphore)
There was a problem hiding this comment.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @janekmi)
tests/multithreaded/common/mtt.c, line 71 at r1 (raw file):
Previously, ldorau (Lukasz Dorau) wrote…
/* * XXX use sem_close() in a for-loop */
sem_unlink()has to be used here too (with the appropriate name of the semaphore)
... so names of the semaphores have to be stored too ...
There was a problem hiding this comment.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @janekmi)
tests/multithreaded/common/mtt.c, line 71 at r1 (raw file):
Previously, ldorau (Lukasz Dorau) wrote…
... so names of the semaphores have to be stored too ...
... or generated here for the 2nd time.
|
Requires proposing a generally useful internal API for synchronizing interrelated execution taking place in two different processes. Closing for now. |
These semaphores are dedicated to interprocess synchronization between the parent and the child processes.
This change is