Re: [LSF/MM/BPF TOPIC] VM Memory Overcommit

["T.J. Alumbaugh" <talumbau@google.com>]

[-- Attachment #1.1: Type: text/plain, Size: 1259 bytes --]

On Wed, Feb 22, 2023 at 4:59 PM T.J. Alumbaugh <talumbau@google.com> wrote:

> Hi,
>
> This topic proposal would be to present and discuss multiple MM
> features to improve host memory overcommit while running VMs. There
> are two general cases:
>
> 1. The host and its guests operate independently,
>
> 2. The host and its guests cooperate by techniques like ballooning.
>
> In the first case, we would discuss some new techniques, e.g., fast
> access bit harvesting in the KVM MMU, and some difficulties, e.g.,
> double zswapping.
>
> In the second case, we would like to discuss a novel working set size
> (WSS) notifier framework and some improvements to the ballooning
> policy. The WSS notifier, when available, can report WSS to its
> listeners. VM Memory Overcommit is one of its use cases: the
> virtio-balloon driver can register for WSS notifications and relay WSS
> to the host. The host can leverage the WSS notifications and improve
> the ballooning policy.
>
> This topic would be of interest to a wide range of audience, e.g.,
> phones, laptops and servers.
> Co-presented with Yuanchu Xie.
>
> Thanks,
>
> -T.J.
>

For completeness, the slide deck that Yuanchu and I presented for this
topic is attached.

[-- Attachment #1.2: Type: text/html, Size: 1662 bytes --]

[-- Attachment #2: LSF_MM_BPF2023_Memory_Overcommit_in_Containerized_Environments.pdf --]
[-- Type: application/pdf, Size: 233345 bytes --]