From: Zi Yan <ziy@nvidia.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH 5/7] khugepaged: Allow to collapse PTE-mapped compound pages
Date: Fri, 27 Mar 2020 14:55:06 -0400 [thread overview]
Message-ID: <D5721ED6-774B-4CD3-8533-4BF9BDB2401E@nvidia.com> (raw)
In-Reply-To: <20200327170601.18563-6-kirill.shutemov@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 3626 bytes --]
On 27 Mar 2020, at 13:05, Kirill A. Shutemov wrote:
> We can collapse PTE-mapped compound pages. We only need to avoid
> handling them more than once: lock/unlock page only once if it's present
> in the PMD range multiple times as it handled on compound level. The
> same goes for LRU isolation and putpack.
s/putpack/putback/
>
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> ---
> mm/khugepaged.c | 41 +++++++++++++++++++++++++++++++----------
> 1 file changed, 31 insertions(+), 10 deletions(-)
>
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index b47edfe57f7b..c8c2c463095c 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -515,6 +515,17 @@ void __khugepaged_exit(struct mm_struct *mm)
>
> static void release_pte_page(struct page *page)
> {
> + /*
> + * We need to unlock and put compound page on LRU only once.
> + * The rest of the pages have to be locked and not on LRU here.
> + */
> + VM_BUG_ON_PAGE(!PageCompound(page) &&
> + (!PageLocked(page) && PageLRU(page)), page);
It only checks base pages.
Add
VM_BUG_ON_PAGE(PageCompound(page) && PageLocked(page) && PageLRU(page), page);
to check for compound pages.
> +
> + if (!PageLocked(page))
> + return;
> +
> + page = compound_head(page);
> dec_node_page_state(page, NR_ISOLATED_ANON + page_is_file_cache(page));
> unlock_page(page);
> putback_lru_page(page);
> @@ -537,6 +548,7 @@ static int __collapse_huge_page_isolate(struct vm_area_struct *vma,
> pte_t *_pte;
> int none_or_zero = 0, result = 0, referenced = 0;
> bool writable = false;
> + LIST_HEAD(compound_pagelist);
>
> for (_pte = pte; _pte < pte+HPAGE_PMD_NR;
> _pte++, address += PAGE_SIZE) {
> @@ -561,13 +573,23 @@ static int __collapse_huge_page_isolate(struct vm_area_struct *vma,
> goto out;
> }
>
> - /* TODO: teach khugepaged to collapse THP mapped with pte */
> + VM_BUG_ON_PAGE(!PageAnon(page), page);
> +
> if (PageCompound(page)) {
> - result = SCAN_PAGE_COMPOUND;
> - goto out;
> - }
> + struct page *p;
> + page = compound_head(page);
>
> - VM_BUG_ON_PAGE(!PageAnon(page), page);
> + /*
> + * Check if we have dealt with the compount page
s/compount/compound/
> + * already
> + */
> + list_for_each_entry(p, &compound_pagelist, lru) {
> + if (page == p)
> + break;
> + }
> + if (page == p)
> + continue;
> + }
>
> /*
> * We can do it before isolate_lru_page because the
> @@ -640,6 +662,9 @@ static int __collapse_huge_page_isolate(struct vm_area_struct *vma,
> page_is_young(page) || PageReferenced(page) ||
> mmu_notifier_test_young(vma->vm_mm, address))
> referenced++;
> +
> + if (PageCompound(page))
> + list_add_tail(&page->lru, &compound_pagelist);
> }
> if (likely(writable)) {
> if (likely(referenced)) {
Do we need a list here? There should be at most one compound page we will see here, right?
If a compound page is seen here, can we bail out the loop early? I guess not,
because we can a partially mapped compound page at the beginning or the end of a VMA, right?
> @@ -1185,11 +1210,7 @@ static int khugepaged_scan_pmd(struct mm_struct *mm,
> goto out_unmap;
> }
>
> - /* TODO: teach khugepaged to collapse THP mapped with pte */
> - if (PageCompound(page)) {
> - result = SCAN_PAGE_COMPOUND;
> - goto out_unmap;
> - }
> + page = compound_head(page);
>
> /*
> * Record which node the original page is from and save this
> --
> 2.26.0
—
Best Regards,
Yan Zi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
next prev parent reply other threads:[~2020-03-27 18:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 17:05 [PATCH 0/7] thp/khugepaged improvements and CoW semantics Kirill A. Shutemov
2020-03-27 17:05 ` [PATCH 1/7] khugepaged: Add self test Kirill A. Shutemov
2020-03-27 17:05 ` [PATCH 2/7] khugepaged: Do not stop collapse if less than half PTEs are referenced Kirill A. Shutemov
2020-03-27 17:30 ` Zi Yan
2020-03-27 17:46 ` Yang Shi
2020-03-27 17:05 ` [PATCH 3/7] khugepaged: Drain LRU add pagevec to get rid of extra pins Kirill A. Shutemov
2020-03-27 17:34 ` Zi Yan
2020-03-28 0:20 ` Kirill A. Shutemov
2020-03-27 18:10 ` Yang Shi
2020-03-28 12:18 ` Kirill A. Shutemov
2020-03-30 18:30 ` Yang Shi
2020-03-30 21:38 ` Kirill A. Shutemov
2020-03-27 17:05 ` [PATCH 4/7] khugepaged: Allow to callapse a page shared across fork Kirill A. Shutemov
2020-03-27 18:19 ` Zi Yan
2020-03-27 21:31 ` Yang Shi
2020-03-27 21:44 ` Zi Yan
2020-03-27 17:05 ` [PATCH 5/7] khugepaged: Allow to collapse PTE-mapped compound pages Kirill A. Shutemov
2020-03-27 18:53 ` Yang Shi
2020-03-28 0:34 ` Kirill A. Shutemov
2020-03-28 1:09 ` Yang Shi
2020-03-28 12:27 ` Kirill A. Shutemov
2020-03-30 18:38 ` Yang Shi
2020-03-27 18:55 ` Zi Yan [this message]
2020-03-28 0:39 ` Kirill A. Shutemov
2020-03-28 1:17 ` Zi Yan
2020-03-28 12:33 ` Kirill A. Shutemov
2020-03-30 18:41 ` Yang Shi
2020-03-30 18:50 ` Yang Shi
2020-03-31 14:08 ` Kirill A. Shutemov
2020-04-01 19:45 ` Yang Shi
2020-03-27 20:45 ` Yang Shi
2020-03-28 0:40 ` Kirill A. Shutemov
2020-03-28 1:12 ` Yang Shi
2020-03-27 17:06 ` [PATCH 6/7] thp: Change CoW semantics for anon-THP Kirill A. Shutemov
2020-03-27 20:07 ` Yang Shi
2020-03-28 0:43 ` Kirill A. Shutemov
2020-03-28 1:30 ` Yang Shi
2020-03-27 17:06 ` [PATCH 7/7] khugepaged: Introduce 'max_ptes_shared' tunable Kirill A. Shutemov
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=D5721ED6-774B-4CD3-8533-4BF9BDB2401E@nvidia.com \
--to=ziy@nvidia.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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