From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Song Liu <songliubraving@fb.com>
Cc: linux-mm@kvack.org, kernel-team@fb.com,
linux-kernel@vger.kernel.org, mhocko@kernel.org,
rientjes@google.com, aarcange@redhat.com
Subject: Re: [PATCH v2] mm/THP: use hugepage_vma_check() in khugepaged_enter_vma_merge()
Date: Mon, 28 May 2018 13:57:24 +0300 [thread overview]
Message-ID: <20180528105724.okg6c7i72r3v3jno@kshutemo-mobl1> (raw)
In-Reply-To: <20180522194430.426688-1-songliubraving@fb.com>
On Tue, May 22, 2018 at 12:44:30PM -0700, Song Liu wrote:
> khugepaged_enter_vma_merge() is using a different approach to check
> whether a vma is valid for khugepaged_enter():
>
> 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 */
> return 0;
>
> This check has some problems. One of the obvious problems is that
> it doesn't check shmem_file(), so that vma backed with shmem files
> will not call khugepaged_enter(). Here is an example of failed madvise():
>
> /* mount /dev/shm with huge=advise:
> * mount -o remount,huge=advise /dev/shm */
> /* create file /dev/shm/huge */
> #define HUGE_FILE "/dev/shm/huge"
>
> fd = open(HUGE_FILE, O_RDONLY);
> ptr = mmap(NULL, FILE_SIZE, PROT_READ, MAP_PRIVATE, fd, 0);
> ret = madvise(ptr, FILE_SIZE, MADV_HUGEPAGE);
>
> madvise() will return 0, but this memory region is never put in huge
> page (check from /proc/meminfo: ShmemHugePages).
>
> This patch fixes these problems by reusing hugepage_vma_check() in
> khugepaged_enter_vma_merge().
>
> vma->vm_flags is not yet updated in khugepaged_enter_vma_merge(),
> so we need to pass the new vm_flags to hugepage_vma_check() through
> a separate argument.
>
> Signed-off-by: Song Liu <songliubraving@fb.com>
> ---
> mm/khugepaged.c | 26 ++++++++++++--------------
> 1 file changed, 12 insertions(+), 14 deletions(-)
>
> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
> index d7b2a4b..9f74e51 100644
> --- a/mm/khugepaged.c
> +++ b/mm/khugepaged.c
> @@ -430,18 +430,15 @@ int __khugepaged_enter(struct mm_struct *mm)
> return 0;
> }
>
> +static bool hugepage_vma_check(struct vm_area_struct *vma,
> + unsigned long vm_flags);
> +
The patch looks good to me.
But can we move hugepage_vma_check() here to avoid forward declaration of
the function?
--
Kirill A. Shutemov
next prev parent reply other threads:[~2018-05-28 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 19:44 Song Liu
2018-05-28 10:57 ` Kirill A. Shutemov [this message]
2018-05-28 18:04 ` 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=20180528105724.okg6c7i72r3v3jno@kshutemo-mobl1 \
--to=kirill@shutemov.name \
--cc=aarcange@redhat.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rientjes@google.com \
--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