linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Shan <gshan@redhat.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>,
	lsf-pc@lists.linux-foundation.org
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: [LSF/MM/BPF TOPIC] Virtual Machine Memory Passthrough
Date: Tue, 21 Feb 2023 10:51:09 +1100	[thread overview]
Message-ID: <fa6d20bd-13d4-9233-758e-012eff558ec3@redhat.com> (raw)
In-Reply-To: <CA+CK2bDr5Xii021JBXeyCEY4jjWCsZQ=ENa-s8MLkBv5hYUvsA@mail.gmail.com>

Hi Pasha,

On 2/21/23 3:31 AM, Pasha Tatashin wrote:
> 
> As a part of an ongoing work of replacing some containerized work load
> with virtual machines within Google, I have worked on making the
> memory translations faster.
> 
> I would like to propose the following topic for this year's LSF/MM/BPF:
> 
> Discuss  a set of techniques that can improve the guest performance,
> memory footprint overhead, observability, and manageability of virtual
> machines by hypervirtualizing the guest memory to the extreme. The end
> goal is to allow very lightweight virtual machines to be closer in
> performance to the containers.
> 
> The following items are going to be discussed in this topic:
> - Reducing the cost of SLAT page table translations.
> - Reducing the memory footprint overhead.
> - Reducing the memory management overhead.
> - Increasing the observability of guest memory.
> 

It's all about to understand the problem and possible solution or directions.

I googled for 'SLAT' and direct me to x86's EPT. ARM64 has similar thing called
stage-2 page table. The usual way to reduce page table translation cost is to map
the contiguous memory through PUD/PMD. I'm not sure if there are other solutions
we're heading for?

Guest's memory is usually backed up by virtual memory area (VMA), which is either
a anonymous or hugetlb region. As I understand, the page fault handling is excessive
to populate the requested memory. I'm not sure if reducing the memory management
overhead is to get it faster, or something else? :)

Thanks,
Gavin



  reply	other threads:[~2023-02-20 23:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 16:31 [LSF/MM/BPF TOPIC] Virtual Machine Memory Passthrough Pasha Tatashin
2023-02-20 23:51 ` Gavin Shan [this message]
2023-02-22 13:43   ` Pasha Tatashin
2023-02-22 15:31     ` Zi Yan
2023-02-22 15:43       ` Pasha Tatashin
2023-02-21  4:38 ` Zhu Yanjun
2023-02-22 13:44   ` Pasha Tatashin
2023-02-22 17:08 ` Gupta, Pankaj
2023-02-22 18:18   ` Pasha Tatashin
2023-02-22 20:27     ` Gupta, Pankaj
2023-02-22 20:56       ` Pasha Tatashin
2023-02-23  9:11         ` Gupta, Pankaj

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=fa6d20bd-13d4-9233-758e-012eff558ec3@redhat.com \
    --to=gshan@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=pasha.tatashin@soleen.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;
as well as URLs for NNTP newsgroup(s).