Re: [PATCH v2 2/2] virtio_balloon: replace oom notifier with shrinker
From: Michal Hocko <mhocko@kernel.org>
Date: 2018-08-02 11:29:01
Possibly related (same subject, not in this thread)
- 2018-08-03 · Re: [PATCH v2 2/2] virtio_balloon: replace oom notifier with shrinker · Wei Wang <hidden>
- 2018-08-02 · Re: [PATCH v2 2/2] virtio_balloon: replace oom notifier with shrinker · "Michael S. Tsirkin" <mst@redhat.com>
- 2018-08-02 · Re: [PATCH v2 2/2] virtio_balloon: replace oom notifier with shrinker · Michal Hocko <mhocko@kernel.org>
- 2018-08-02 · Re: [PATCH v2 2/2] virtio_balloon: replace oom notifier with shrinker · Wei Wang <hidden>
- 2018-08-02 · Re: [PATCH v2 2/2] virtio_balloon: replace oom notifier with shrinker · Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
On Thu 02-08-18 19:27:40, Wei Wang wrote:
On 08/02/2018 07:00 PM, Tetsuo Handa wrote:quoted
On 2018/08/02 19:32, Wei Wang wrote:quoted
On 08/01/2018 07:34 PM, Michal Hocko wrote:quoted
Do you have any numbers for how does this work in practice?It works in this way: for example, we can set the parameter, balloon_pages_to_shrink, to shrink 1GB memory once shrink scan is called. Now, we have a 8GB guest, and we balloon out 7GB. When shrink scan is called, the balloon driver will get back 1GB memory and give them back to mm, then the ballooned memory becomes 6GB.Since shrinker might be called concurrently (am I correct?),Not sure about it being concurrently, but I think it would be called repeatedly as should_continue_reclaim() returns true.
Multiple direct reclaimers might indeed invoke it concurrently. -- Michal Hocko SUSE Labs