From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: <david@redhat.com>, <linux-mm@kvack.org>, <dave.hansen@intel.com>,
<tim.c.chen@intel.com>, <ying.huang@intel.com>
Subject: Re: [RFC PATCH 5/5] filemap: batched update mm counter,rmap when map file folio
Date: Tue, 31 Jan 2023 09:11:54 +0800 [thread overview]
Message-ID: <9aa5c3e5-1742-b739-08a3-fab609ec7be1@intel.com> (raw)
In-Reply-To: <Y9fQxtMeF8QyQanu@casper.infradead.org>
On 1/30/2023 10:14 PM, Matthew Wilcox wrote:
> On Mon, Jan 30, 2023 at 08:55:04PM +0800, Yin Fengwei wrote:
>> +++ b/mm/filemap.c
>> @@ -3360,28 +3360,52 @@ static vm_fault_t filemap_map_folio_range(struct vm_fault *vmf,
>> struct vm_area_struct *vma = vmf->vma;
>> struct file *file = vma->vm_file;
>> unsigned int mmap_miss = READ_ONCE(file->f_ra.mmap_miss);
>> - int ref_count = 0, count = 0;
>> + int ref_count = 0, count = 0, maplen = 0;
>> + struct page *pg = page;
>
> OK, having read it through, I think you're making your life a lot harder
> by keeping page pointers at all. I'd pass xas.xa_index - folio->index
> from filemap_map_pages() as a parameter called something like 'first'.
I use page pointer here because I saw other changes you made kept the
page pointer as parameter. And tried to align with that.
>
>> do {
>> - if (PageHWPoison(page))
>> + if (PageHWPoison(page)) {
>> + if (maplen) {
>> + page_add_file_rmap_range(folio, pg, maplen,
>> + vma, false);
>> + add_mm_counter(vma->vm_mm,
>> + mm_counter_file(pg), maplen);
>
> Again you've made your life harder ;-) Try something like this:
Yes. This is much better.
>
> void do_set_pte(struct vm_fault *vmf, struct page *page, unsigned long addr)
> {
> do_set_pte_range(vmf, page, addr, 1);
> }
>
> ... and then here, you can do:
>
> if (maplen)
> do_set_pte_range(vmf, page - maplen - 1,
> base_addr, maplen);
> base_addr += (maplen + 1) * PAGE_SIZE
> maplen = 0;
> continue;
Thanks a lot for all your comments. I will address all your comments in
next version.
Regards
Yin, Fengwei
>
next prev parent reply other threads:[~2023-01-31 1:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 12:54 [RFC PATCH 0/5] folio based filemap_map_pages() Yin Fengwei
2023-01-30 12:55 ` [RFC PATCH 1/5] mm: Enable fault around for shared file page fault Yin Fengwei
2023-01-30 13:21 ` Matthew Wilcox
2023-01-31 0:59 ` Yin, Fengwei
2023-01-30 12:55 ` [RFC PATCH 2/5] filemap: do file page mapping with folio granularity Yin Fengwei
2023-01-30 13:35 ` Matthew Wilcox
2023-01-31 1:03 ` Yin, Fengwei
2023-01-31 3:34 ` Huang, Ying
2023-01-31 6:32 ` Yin, Fengwei
2023-01-30 12:55 ` [RFC PATCH 3/5] rmap: add page_add_file_rmap_range() Yin Fengwei
2023-01-30 13:50 ` Matthew Wilcox
2023-01-31 7:24 ` Huang, Ying
2023-01-31 7:48 ` Yin, Fengwei
2023-01-30 12:55 ` [RFC PATCH 4/5] mm: add do_set_pte_entry() Yin Fengwei
2023-01-30 13:53 ` Matthew Wilcox
2023-01-31 1:06 ` Yin, Fengwei
2023-01-30 12:55 ` [RFC PATCH 5/5] filemap: batched update mm counter,rmap when map file folio Yin Fengwei
2023-01-30 14:14 ` Matthew Wilcox
2023-01-31 1:11 ` Yin, Fengwei [this message]
2023-01-30 12:58 ` [RFC PATCH 0/5] folio based filemap_map_pages() Yin, Fengwei
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=9aa5c3e5-1742-b739-08a3-fab609ec7be1@intel.com \
--to=fengwei.yin@intel.com \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=tim.c.chen@intel.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.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