linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Peng Zhang <zhangpeng362@huawei.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, fengwei.yin@intel.com,
	ying.huang@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: Fri, 24 Nov 2023 06:05:05 +0000	[thread overview]
Message-ID: <ZWA9EVlsuHIBi0xb@casper.infradead.org> (raw)
In-Reply-To: <20231122140052.4092083-1-zhangpeng362@huawei.com>

On Wed, Nov 22, 2023 at 10:00:52PM +0800, Peng Zhang wrote:
> 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().

What I haven't quite understood yet is why we need to set the pte to
zero on x86 in the specific case of do_numa_page().  I understand that
ppc needs to.

Could someone explain why the _default_ definition of
ptep_modify_prot_start() is not:

+++ b/include/linux/pgtable.h
@@ -1074,7 +1074,7 @@ static inline pte_t ptep_modify_prot_start(struct vm_area_struct *vma,
                                           unsigned long addr,
                                           pte_t *ptep)
 {
-       return __ptep_modify_prot_start(vma, addr, ptep);
+       return *ptep;
 }

 /*



  parent reply	other threads:[~2023-11-24  6:05 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
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 [this message]
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=ZWA9EVlsuHIBi0xb@casper.infradead.org \
    --to=willy@infradead.org \
    --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=ying.huang@intel.com \
    --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