From: David Hildenbrand <david@redhat.com>
To: Rik van Riel <riel@surriel.com>,
Linux Memory Management List <linux-mm@kvack.org>
Cc: Minchan Kim <minchan@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Peter Xu <peterx@redhat.com>
Subject: Re: Page zapping and page table reclaim
Date: Thu, 18 Mar 2021 19:15:34 +0100 [thread overview]
Message-ID: <cd00efdc-fe73-e0a4-8a3a-1e2f98294121@redhat.com> (raw)
In-Reply-To: <9d610d214ed8fcea9a236ec2fc54c39a5a841497.camel@surriel.com>
On 18.03.21 19:03, Rik van Riel wrote:
> On Thu, 2021-03-11 at 19:14 +0100, David Hildenbrand wrote:
>> Hi folks,
>>
>> I was wondering, is there any mechanism that reclaims basically
>> empty
>> page tables in a running process?
>
> Currently we have do_munmap -> unmap_region -> free_pgtables,
> which is hooked up only to sys_munmap.
>
> We don't seem to have an equivalent for the various MADV_
> options that lead to freed memory.
>
The other path I am interested in is doing an
fallocate(FALLOC_FL_PUNCH_HOLE)/MADV_REMOVE on a shared file/mapping,
resulting in the same situation AFAIKS.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-03-18 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 18:14 Page zapping and page table reclaim David Hildenbrand
2021-03-11 21:26 ` Peter Xu
2021-03-11 21:35 ` David Hildenbrand
2021-03-19 17:04 ` Yang Shi
2021-03-22 9:34 ` David Hildenbrand
2021-03-18 16:57 ` Vlastimil Babka
2021-03-18 23:53 ` Balbir Singh
2021-03-19 12:44 ` David Hildenbrand
2021-03-20 1:56 ` Balbir Singh
2021-03-22 9:19 ` David Hildenbrand
2021-03-18 18:03 ` Rik van Riel
2021-03-18 18:15 ` David Hildenbrand [this message]
2021-03-24 9:55 ` David Hildenbrand
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=cd00efdc-fe73-e0a4-8a3a-1e2f98294121@redhat.com \
--to=david@redhat.com \
--cc=aarcange@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=peterx@redhat.com \
--cc=riel@surriel.com \
--cc=willy@infradead.org \
/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).