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
Migrate vmm_callout -> OSX libdispatch #112
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please squash fixup commits into earlier commits in the series.
Have you done any performance comparisons before and after your changes? |
Just rebased on master. |
Tried the Tiny Linux boot, and it still works with the rebased version. I have run performance tests in the past (2 years ago) and they looked better than the original implementation (and if I just could remember how did I they looked like!). What would you suggest, how to exercise it? I think it would make sense to test it again. |
@machyve/write-access do you think this still something that is worth to merge? I can try to spend some time on it to get it tested again. |
…urrency bug. The bug may occur in callout_stop_safe when queued is still not 0 and we call dispatch_suspend on a released object, can happen only during draining.
@bonifaido it seems like project is semi-dead. |
@jeremyhu can you take a look on this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks.
Migrate vmm_callout -> OSX libdispatch (machyve#112)
Tries to be a cleaner implementation then the current one, based upon what I saw in README.md - TODO I thought it was a good idea to migrate it. I wouldn't say it is complete, but it could be a good starting point. I haven't seen any issues by running a VM for a couple of hours with multiple sleeps with this patch.