linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: Peng Zhang <zhangpeng362@huawei.com>
Cc: <linux-mm@kvack.org>,  <linux-kernel@vger.kernel.org>,
	<akpm@linux-foundation.org>,  <willy@infradead.org>,
	<fengwei.yin@intel.com>,  <aneesh.kumar@linux.ibm.com>,
	<shy828301@gmail.com>,  <hughd@google.com>,  <david@redhat.com>,
	<wangkefeng.wang@huawei.com>,  <sunnanyong@huawei.com>
Subject: Re: [RFC PATCH] mm: filemap: avoid unnecessary major faults in filemap_fault()
Date: Thu, 23 Nov 2023 16:36:20 +0800	[thread overview]
Message-ID: <87a5r4988r.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <20231122140052.4092083-1-zhangpeng362@huawei.com> (Peng Zhang's message of "Wed, 22 Nov 2023 22:00:52 +0800")

Peng Zhang <zhangpeng362@huawei.com> writes:

> From: ZhangPeng <zhangpeng362@huawei.com>
>
> The major fault occurred when using mlockall(MCL_CURRENT | MCL_FUTURE)
> in application, which leading to an unexpected performance issue[1].
>
> This caused by temporarily cleared pte during a read/modify/write update
> of the pte, eg, do_numa_page()/change_pte_range().
>
> For the data segment of the user-mode program, the global variable area
> is a private mapping. After the pagecache is loaded, the private anonymous
> page is generated after the COW is triggered. Mlockall can lock COW pages
> (anonymous pages), but the original file pages cannot be locked and may
> be reclaimed. If the global variable (private anon page) is accessed when
> vmf->pte is zeroed in numa fault, a file page fault will be triggered.
>
> At this time, the original private file page may have been reclaimed.
> If the page cache is not available at this time, a major fault will be
> triggered and the file will be read, causing additional overhead.
>
> Fix this by rechecking the pte by holding ptl in filemap_fault() before
> triggering a major fault.
>
> [1] https://lore.kernel.org/linux-mm/9e62fd9a-bee0-52bf-50a7-498fa17434ee@huawei.com/
>
> Signed-off-by: ZhangPeng <zhangpeng362@huawei.com>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>

Suggested-by: "Huang, Ying" <ying.huang@intel.com>

:-)

> ---
>  mm/filemap.c | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
>
> diff --git a/mm/filemap.c b/mm/filemap.c
> index 71f00539ac00..bb5e6a2790dc 100644
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -3226,6 +3226,20 @@ vm_fault_t filemap_fault(struct vm_fault *vmf)
>  			mapping_locked = true;
>  		}
>  	} else {
> +		pte_t *ptep = pte_offset_map_lock(vmf->vma->vm_mm, vmf->pmd,
> +						  vmf->address, &vmf->ptl);
> +		if (ptep) {
> +			/*
> +			 * Recheck pte with ptl locked as the pte can be cleared
> +			 * temporarily during a read/modify/write update.
> +			 */
> +			if (unlikely(!pte_none(ptep_get(ptep))))
> +				ret = VM_FAULT_NOPAGE;
> +			pte_unmap_unlock(ptep, vmf->ptl);
> +			if (unlikely(ret))
> +				return ret;
> +		}
> +

Need to deal with ptep == NULL.  Although that is high impossible.

--
Best Regards,
Huang, Ying

>  		/* No page in the page cache at all */
>  		count_vm_event(PGMAJFAULT);
>  		count_memcg_event_mm(vmf->vma->vm_mm, PGMAJFAULT);


  parent reply	other threads:[~2023-11-23  8:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 14:00 Peng Zhang
2023-11-23  1:09 ` Yin Fengwei
2023-11-23  4:12   ` zhangpeng (AS)
2023-11-23  5:26     ` Yin Fengwei
2023-11-23  7:57       ` zhangpeng (AS)
2023-11-23  8:29         ` Yin Fengwei
2023-11-23  9:09           ` zhangpeng (AS)
2023-11-24  4:13         ` Huang, Ying
2023-11-24  4:26           ` Huang, Ying
2023-11-24  7:27             ` zhangpeng (AS)
2023-11-24  8:04               ` Huang, Ying
2023-11-29  1:24                 ` zhangpeng (AS)
2023-11-29  2:59                   ` Huang, Ying
2024-02-01 12:10                     ` zhangpeng (AS)
2024-02-02  0:39                       ` Huang, Ying
2024-02-02  3:31                         ` zhangpeng (AS)
2023-11-24  7:26           ` zhangpeng (AS)
2023-11-23  8:36 ` Huang, Ying [this message]
2023-11-23  9:09   ` zhangpeng (AS)
2023-11-23 15:33     ` Matthew Wilcox
2023-11-24  2:04       ` zhangpeng (AS)
2023-11-24  7:26   ` zhangpeng (AS)
2023-11-24  7:59     ` Huang, Ying
2023-11-24  6:05 ` Matthew Wilcox
2023-11-24  7:43   ` zhangpeng (AS)

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=87a5r4988r.fsf@yhuang6-desk2.ccr.corp.intel.com \
    --to=ying.huang@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=fengwei.yin@intel.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shy828301@gmail.com \
    --cc=sunnanyong@huawei.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=willy@infradead.org \
    --cc=zhangpeng362@huawei.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