Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-process instead of multi-threaded #13

Open
libv opened this issue Mar 9, 2020 · 1 comment
Open

Multi-process instead of multi-threaded #13

libv opened this issue Mar 9, 2020 · 1 comment
Assignees

Comments

@libv
Copy link
Collaborator

libv commented Mar 9, 2020

Use SHM for shared kms fd and shared data.

The current design is threaded, so we cannot easily restart things. By making it multi-process, we can send signals to individual processes.

Depends on issue #10

@libv
Copy link
Collaborator Author

libv commented Nov 14, 2020

SHM is not a solution. While mutex can be made robust (so they can catch process dying), this is no true for pthread_cond, even though the latter can be set to "shared", which makes one assume that sharing these sensibly across processes is a good thing to do.

Giving up on SHM, moving to sockets. 2.5manweeks burned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant