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

Improve the locking mechanism in memory hotplug/unplug operation #57

Open
yb01 opened this issue Aug 31, 2020 · 0 comments
Open

Improve the locking mechanism in memory hotplug/unplug operation #57

yb01 opened this issue Aug 31, 2020 · 0 comments

Comments

@yb01
Copy link
Collaborator

yb01 commented Aug 31, 2020

Currently as the initial implmentation, the vm resource update in progress flag is set up inthe runtime so that we can ignore the incoming resource update in the CRI function. however the reset of the flag comes from the libvirt callback function which has to be in separate handler code. code maintainness, logic complexity is there with this approach.

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