Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Support the memory hotplugged remove #792

Closed
wants to merge 2 commits into from

Conversation

BetaXOi
Copy link

@BetaXOi BetaXOi commented Sep 27, 2018

Fix: #791

@amshinde
Copy link
Member

amshinde commented Oct 8, 2018

@BetaXOi Can you fix your commit message to include a subsystem and a description.
Please refer to the Contribution guidelines here:
https://github.com/kata-containers/community/blob/master/CONTRIBUTING.md#patch-format

cc @jcvenegas Can you take a look, since you have looking at memory hotplug/unplug.

@bergwolf
Copy link
Member

bergwolf commented Oct 9, 2018

I think we've decided to look at balloon and virtio-mem first.

@jcvenegas
Copy link
Member

@BetaXOi as first step we are going to balloon + hotplug , I still would like to evaluate this approach in order to remove memory slots, but first I want to get numbers about the time it takes to remove an slot
under an stressed system. Lets work on that to get a clear about idea about it :). But also as @bergwolf mentioned, for longer term solution we are evaluating to virtio-mem.

@raravena80
Copy link
Member

@BetaXOi ping, any updates?

@BetaXOi BetaXOi closed this Nov 9, 2018
@BetaXOi BetaXOi deleted the master branch November 15, 2018 06:17
egernst pushed a commit to egernst/runtime that referenced this pull request Feb 9, 2021
…ces-access

device: Do not allow container access to the nvdimm rootfs
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants