From: Rik van Riel <riel@surriel.com>
To: Song Liu <songliubraving@fb.com>, linux-mm@kvack.org
Cc: kernel-team@fb.com, linux-kernel@vger.kernel.org,
Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: [PATCH] mm/THP: use hugepage_vma_check() in khugepaged_enter_vma_merge()
Date: Mon, 21 May 2018 15:53:02 -0400 [thread overview]
Message-ID: <1526932382.7898.25.camel@surriel.com> (raw)
In-Reply-To: <20180521193853.3089484-1-songliubraving@fb.com>
[-- Attachment #1: Type: text/plain, Size: 1665 bytes --]
On Mon, 2018-05-21 at 12:38 -0700, Song Liu wrote:
> This patch fixes these problems by reusing hugepage_vma_check() in
> khugepaged_enter_vma_merge().
Lets take a look at this in more detail. This effectively
adds the following conditions to khugepaged_enter_vma_merge:
- fail if MMF_DISABLE_THP bit is set in mm->flags (good)
- allow if merging a tmpfs file and THP tmpfs is enabled (good)
- disallow if is_vma_temporary_stack (good)
- otherwise, allow if !VM_NO_KHUGEPAGED flag (good)
Looks like this covers all the conditions I can think
of, and if I missed any, chances are that condition
should be added to hugepage_vma_check()...
> Signed-off-by: Song Liu <songliubraving@fb.com>
Reviewed-by: Rik van Riel <riel@surriel.com>
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index d7b2a4b..e50c2bd 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -430,18 +430,14 @@ int __khugepaged_enter(struct mm_struct *mm)
> return 0;
> }
>
> +static bool hugepage_vma_check(struct vm_area_struct *vma);
> +
> int khugepaged_enter_vma_merge(struct vm_area_struct *vma,
> unsigned long vm_flags)
> {
> unsigned long hstart, hend;
> - if (!vma->anon_vma)
> - /*
> - * Not yet faulted in so we will register later in
> the
> - * page fault if needed.
> - */
> - return 0;
> - if (vma->vm_ops || (vm_flags & VM_NO_KHUGEPAGED))
> - /* khugepaged not yet working on file or special
> mappings */
> +
> + if (!hugepage_vma_check(vma))
> return 0;
> hstart = (vma->vm_start + ~HPAGE_PMD_MASK) & HPAGE_PMD_MASK;
> hend = vma->vm_end & HPAGE_PMD_MASK;
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-05-21 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 19:38 Song Liu
2018-05-21 19:53 ` Rik van Riel [this message]
2018-05-21 21:19 ` David Rientjes
2018-05-22 12:13 ` Michal Hocko
2018-05-22 19:31 ` Song Liu
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=1526932382.7898.25.camel@surriel.com \
--to=riel@surriel.com \
--cc=aarcange@redhat.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=songliubraving@fb.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