From: David Hildenbrand <david@redhat.com>
To: Mike Kravetz <mike.kravetz@oracle.com>,
fei luo <morphyluo@gmail.com>,
akpm@linux-foundation.org, arnd@arndb.de,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org
Cc: Joao Martins <joao.m.martins@oracle.com>
Subject: Re: [RFD] clear virtual machine memory when virtual machine is turned off
Date: Fri, 3 Dec 2021 19:20:45 +0100 [thread overview]
Message-ID: <1e0ce8f6-332b-399f-5ac7-5a56639172b3@redhat.com> (raw)
In-Reply-To: <e13bd5e9-981f-e2f1-fdd9-049a1926d70f@oracle.com>
On 02.12.21 18:27, Mike Kravetz wrote:
> On 12/2/21 04:47, David Hildenbrand wrote:
>> On 02.12.21 11:19, fei luo wrote:
>>>
>>> When reusing the page that has been cleared, there is no need to clear it
>>>
>>> again, which also speeds up the memory allocation of user-mode programs.
>>>
>>>
>>> Is this feature feasible?
>>
>> "init_on_free=1" for the system as a whole, which might sounds like what
>> might tackle part of your use case.
>>
>
> Certainly init_on_free will not make much difference if VMs are backed by
> hugetlb pages. We (Joao and myself) have thought about clearing hugetlb
> pages from user space in an attempt speed up launching of VMs backed by
> hugetlb pages.
>
I remember that discussion. And I also recall a discussion regarding
extending init_on_free semantics to hugetlbfs.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-12-03 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 10:19 [RFD] clear virtual machine memory when virtual machine is turned off fei luo
2021-12-02 12:47 ` David Hildenbrand
2021-12-02 17:27 ` Mike Kravetz
2021-12-03 18:20 ` David Hildenbrand [this message]
2021-12-03 2:56 ` fei luo
2021-12-03 18:20 ` David Hildenbrand
2021-12-02 10:41 [RFD] Clear " fei luo
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=1e0ce8f6-332b-399f-5ac7-5a56639172b3@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=joao.m.martins@oracle.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=morphyluo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.