From: "zhangpeng (AS)" <zhangpeng362@huawei.com>
To: Sidhartha Kumar <sidhartha.kumar@oracle.com>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Cc: <akpm@linux-foundation.org>, <willy@infradead.org>
Subject: Re: [PATCH 4/4] mm/memory: convert do_read_fault() to use folios
Date: Mon, 3 Jul 2023 17:29:54 +0800 [thread overview]
Message-ID: <4128bc10-5110-983c-192f-afe8b856b329@huawei.com> (raw)
In-Reply-To: <20230703055850.227169-4-sidhartha.kumar@oracle.com>
On 2023/7/3 13:58, Sidhartha Kumar wrote:
> Saves one implicit call to compound_head()
>
> Signed-off-by: Sidhartha Kumar <sidhartha.kumar@oracle.com>
Reviewed-by: ZhangPeng <zhangpeng362@huawei.com>
> ---
> mm/memory.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/mm/memory.c b/mm/memory.c
> index 33bf13431974c..b97c66df4adac 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -4528,6 +4528,7 @@ static inline bool should_fault_around(struct vm_fault *vmf)
> static vm_fault_t do_read_fault(struct vm_fault *vmf)
> {
> vm_fault_t ret = 0;
> + struct folio *folio = page_folio(vmf->page);
>
> /*
> * Let's call ->map_pages() first and use ->fault() as fallback
> @@ -4545,9 +4546,9 @@ static vm_fault_t do_read_fault(struct vm_fault *vmf)
> return ret;
>
> ret |= finish_fault(vmf);
> - unlock_page(vmf->page);
> + folio_unlock(folio);
> if (unlikely(ret & (VM_FAULT_ERROR | VM_FAULT_NOPAGE | VM_FAULT_RETRY)))
> - put_page(vmf->page);
> + folio_put(folio);
> return ret;
> }
>
next prev parent reply other threads:[~2023-07-03 9:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 5:58 [PATCH 1/4] mm/memory: convert do_page_mkwrite() " Sidhartha Kumar
2023-07-03 5:58 ` [PATCH 2/4] mm/memory: convert wp_page_shared() " Sidhartha Kumar
2023-07-03 9:29 ` zhangpeng (AS)
2023-07-03 23:29 ` Matthew Wilcox
2023-07-03 5:58 ` [PATCH 3/4] mm/memory: convert do_shared_fault() to folios Sidhartha Kumar
2023-07-03 9:29 ` zhangpeng (AS)
2023-07-03 22:05 ` SeongJae Park
2023-07-04 2:25 ` Sidhartha Kumar
2023-07-03 23:31 ` Matthew Wilcox
2023-07-04 2:18 ` Sidhartha Kumar
2023-07-03 5:58 ` [PATCH 4/4] mm/memory: convert do_read_fault() to use folios Sidhartha Kumar
2023-07-03 9:29 ` zhangpeng (AS) [this message]
2023-07-03 23:32 ` Matthew Wilcox
2023-07-03 9:29 ` [PATCH 1/4] mm/memory: convert do_page_mkwrite() " zhangpeng (AS)
2023-07-03 23:25 ` Matthew Wilcox
2023-07-04 19:35 ` Matthew Wilcox
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=4128bc10-5110-983c-192f-afe8b856b329@huawei.com \
--to=zhangpeng362@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sidhartha.kumar@oracle.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