From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
Matthew Wilcox <willy@infradead.org>,
David Hildenbrand <david@redhat.com>,
Sidhartha Kumar <sidhartha.kumar@oracle.com>,
Vishal Moola <vishal.moola@gmail.com>
Subject: Re: [PATCH v3 5/5] mm: memory: use folio_prealloc() in wp_page_copy()
Date: Sat, 18 Nov 2023 10:43:01 +0800 [thread overview]
Message-ID: <153d0e8e-c860-4221-bcb0-71b46f17e2d5@huawei.com> (raw)
In-Reply-To: <20231118023232.1409103-6-wangkefeng.wang@huawei.com>
On 2023/11/18 10:32, Kefeng Wang wrote:
> Use folio_prealloc() helper to simplify code a bit.
>
Forget to add RB of Vishal,adding it
Reviewed-by: Vishal Moola (Oracle) <vishal.moola@gmail.com>
> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
> ---
> mm/memory.c | 22 +++++++---------------
> 1 file changed, 7 insertions(+), 15 deletions(-)
>
> diff --git a/mm/memory.c b/mm/memory.c
> index 868a2fc54549..98d9c7094cab 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -3112,6 +3112,7 @@ static vm_fault_t wp_page_copy(struct vm_fault *vmf)
> int page_copied = 0;
> struct mmu_notifier_range range;
> vm_fault_t ret;
> + bool pfn_is_zero;
>
> delayacct_wpcopy_start();
>
> @@ -3121,16 +3122,13 @@ static vm_fault_t wp_page_copy(struct vm_fault *vmf)
> if (unlikely(ret))
> goto out;
>
> - if (is_zero_pfn(pte_pfn(vmf->orig_pte))) {
> - new_folio = vma_alloc_zeroed_movable_folio(vma, vmf->address);
> - if (!new_folio)
> - goto oom;
> - } else {
> + pfn_is_zero = is_zero_pfn(pte_pfn(vmf->orig_pte));
> + new_folio = folio_prealloc(mm, vma, vmf->address, pfn_is_zero);
> + if (!new_folio)
> + goto oom;
> +
> + if (!pfn_is_zero) {
> int err;
> - new_folio = vma_alloc_folio(GFP_HIGHUSER_MOVABLE, 0, vma,
> - vmf->address, false);
> - if (!new_folio)
> - goto oom;
>
> err = __wp_page_copy_user(&new_folio->page, vmf->page, vmf);
> if (err) {
> @@ -3151,10 +3149,6 @@ static vm_fault_t wp_page_copy(struct vm_fault *vmf)
> kmsan_copy_page_meta(&new_folio->page, vmf->page);
> }
>
> - if (mem_cgroup_charge(new_folio, mm, GFP_KERNEL))
> - goto oom_free_new;
> - folio_throttle_swaprate(new_folio, GFP_KERNEL);
> -
> __folio_mark_uptodate(new_folio);
>
> mmu_notifier_range_init(&range, MMU_NOTIFY_CLEAR, 0, mm,
> @@ -3253,8 +3247,6 @@ static vm_fault_t wp_page_copy(struct vm_fault *vmf)
>
> delayacct_wpcopy_end();
> return 0;
> -oom_free_new:
> - folio_put(new_folio);
> oom:
> ret = VM_FAULT_OOM;
> out:
prev parent reply other threads:[~2023-11-18 2:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 2:32 [PATCH v3 0/5] mm: cleanup and use more folio in page fault Kefeng Wang
2023-11-18 2:32 ` [PATCH v3 1/5] mm: ksm: use more folio api in ksm_might_need_to_copy() Kefeng Wang
2023-11-18 2:32 ` [PATCH v3 2/5] mm: memory: use a folio in validate_page_before_insert() Kefeng Wang
2023-11-18 2:32 ` [PATCH v3 3/5] mm: memory: rename page_copy_prealloc() to folio_prealloc() Kefeng Wang
2023-11-18 2:32 ` [PATCH v3 4/5] mm: memory: use a folio in do_cow_fault() Kefeng Wang
2023-11-18 2:32 ` [PATCH v3 5/5] mm: memory: use folio_prealloc() in wp_page_copy() Kefeng Wang
2023-11-18 2:43 ` Kefeng Wang [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=153d0e8e-c860-4221-bcb0-71b46f17e2d5@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sidhartha.kumar@oracle.com \
--cc=vishal.moola@gmail.com \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®