linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@fb.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	Kernel Team <Kernel-team@fb.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Kirill A. Shutemov" <kirill@shutemov.name>
Subject: Re: [PATCH] mm/THP: use hugepage_vma_check() in khugepaged_enter_vma_merge()
Date: Tue, 22 May 2018 19:31:31 +0000	[thread overview]
Message-ID: <714CDE40-F3F2-4366-8765-C738EC66D8FD@fb.com> (raw)
In-Reply-To: <20180522121319.GB30663@dhcp22.suse.cz>

On May 22, 2018, at 5:13 AM, Michal Hocko <mhocko@kernel.org> wrote:
> 
> [CC Kirill]
> 
> On Mon 21-05-18 12:38:53, 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().
>> 
>> This patch fixes these problems by reusing hugepage_vma_check() in
>> khugepaged_enter_vma_merge().
> 
> It would be great to be more explicit about what are the actual
> consequences. khugepaged_enter_vma_merge is called from multiple
> context. Some of then do not really care about !anon case (e.g. stack
> expansion). hugepage_madvise is quite convoluted so I am not really sure
> from a quick look (are we simply not going to merge vmas even if we
> could?).

Yes, it does fix madvise for shmem with huge=advise option. I had made
a mistake in this version. I will send v2 with the more details on what
is fixed. 

> Have you noticed this by a code inspection or you have seen this
> happening in real workloads (aka, is this worth backporting to stable
> trees)?

I noticed this when reading the code. I think this might worth back 
porting. However, I don't know whether it fixes anything else other
than shmem, so I am not sure which versions need this fix. 

Thanks,
Song


>> Signed-off-by: Song Liu <songliubraving@fb.com>
>> ---
>> mm/khugepaged.c | 12 ++++--------
>> 1 file changed, 4 insertions(+), 8 deletions(-)
>> 
>> 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;
>> -- 
>> 2.9.5
> 
> -- 
> Michal Hocko
> SUSE Labs

      reply	other threads:[~2018-05-22 19:31 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
2018-05-21 21:19 ` David Rientjes
2018-05-22 12:13 ` Michal Hocko
2018-05-22 19:31   ` Song Liu [this message]

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=714CDE40-F3F2-4366-8765-C738EC66D8FD@fb.com \
    --to=songliubraving@fb.com \
    --cc=Kernel-team@fb.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.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