linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "T.J. Alumbaugh" <talumbau@google.com>
To: lsf-pc@lists.linux-foundation.org
Cc: "Sudarshan Rajagopalan (QUIC)" <quic_sudaraja@quicinc.com>,
	hch@lst.de, kai.huang@intel.com,
	 David Hildenbrand <david@redhat.com>,
	jon@nutanix.com, Yuanchu Xie <yuanchu@google.com>,
	 linux-mm <linux-mm@kvack.org>
Subject: [LSF/MM/BPF TOPIC] VM Memory Overcommit
Date: Wed, 22 Feb 2023 16:59:26 -0700	[thread overview]
Message-ID: <CABmGT5H6t_agW=yY1U78tsV+chLoRf2=mcSc8GCYUD25PbxahQ@mail.gmail.com> (raw)

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.


             reply	other threads:[~2023-02-23  0:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 23:59 T.J. Alumbaugh [this message]
2023-02-28  6:02 ` Gupta, Pankaj
2023-03-01  3:09   ` T.J. Alumbaugh
2023-02-28  9:20 ` David Hildenbrand
2023-02-28 22:38   ` SeongJae Park
2023-02-28 22:52     ` David Hildenbrand
2023-03-02  3:26       ` David Rientjes
2023-03-02  9:32         ` David Hildenbrand
2023-03-01  3:21   ` T.J. Alumbaugh
2023-05-19 21:39 ` T.J. Alumbaugh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABmGT5H6t_agW=yY1U78tsV+chLoRf2=mcSc8GCYUD25PbxahQ@mail.gmail.com' \
    --to=talumbau@google.com \
    --cc=david@redhat.com \
    --cc=hch@lst.de \
    --cc=jon@nutanix.com \
    --cc=kai.huang@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=quic_sudaraja@quicinc.com \
    --cc=yuanchu@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox