From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Zhu Yanjun <zyjzyj2000@gmail.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm <linux-mm@kvack.org>
Subject: Re: [LSF/MM/BPF TOPIC] Virtual Machine Memory Passthrough
Date: Wed, 22 Feb 2023 08:44:36 -0500 [thread overview]
Message-ID: <CA+CK2bDrs-pWOP5Phbcd1rdJ_5riHgcZasS_ZJzf2DLT6Q=_2A@mail.gmail.com> (raw)
In-Reply-To: <CAD=hENeJKYzvjM+8wgx60w7VJM-nsDoSRS9hXX6YSaiWXEFbfw@mail.gmail.com>
On Mon, Feb 20, 2023 at 11:38 PM Zhu Yanjun <zyjzyj2000@gmail.com> wrote:
>
> On Tue, Feb 21, 2023 at 12:32 AM Pasha Tatashin
> <pasha.tatashin@soleen.com> wrote:
> >
> > Hello,
> >
> > 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.
>
> Intel's implementation of SLAT, known as Extended Page Table (EPT),
> was introduced in the Nehalem microarchitecture found in certain Core
> i7, Core i5, and Core i3 processors.
> ARM's virtualization extensions support SLAT, known as Stage-2
> page-tables provided by a Stage-2 MMU. The guest uses the Stage-1 MMU.
> Support was added as optional in the ARMv7ve architecture and is also
> supported in the ARMv8 (32-bit and 64-bit) architectures.
> I am interested in this. Hope we have a better solution to reduce the
> cost of SLAT.
Hi Zhu,
Please take a look at my previous reply to Gavin Shan where I clarify
the SLAT performance improvements.
Thanks,
Pasha
>
> > - Reducing the memory footprint overhead.
> > - Reducing the memory management overhead.
> > - Increasing the observability of guest memory.
> >
next prev parent reply other threads:[~2023-02-22 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 16:31 Pasha Tatashin
2023-02-20 23:51 ` Gavin Shan
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 [this message]
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='CA+CK2bDrs-pWOP5Phbcd1rdJ_5riHgcZasS_ZJzf2DLT6Q=_2A@mail.gmail.com' \
--to=pasha.tatashin@soleen.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=zyjzyj2000@gmail.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