From: David Hildenbrand <david@redhat.com>
To: "Yin, Fengwei" <fengwei.yin@intel.com>,
Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, dave.hansen@intel.com, tim.c.chen@intel.com,
ying.huang@intel.com
Subject: Re: [RFC PATCH] mm: populate multiple PTEs if file page is large folio
Date: Tue, 17 Jan 2023 11:37:05 +0100 [thread overview]
Message-ID: <e14b4e9a-612d-fc02-edc0-8f3b6bcf4148@redhat.com> (raw)
In-Reply-To: <2100e7c9-2a5c-4c1a-6e22-9710a2b0c66f@intel.com>
On 17.01.23 10:19, Yin, Fengwei wrote:
>
>
> On 1/14/2023 2:13 AM, Matthew Wilcox wrote:
>> On Sat, Jan 14, 2023 at 12:35:38AM +0800, Yin Fengwei wrote:
>>> The page fault number can be reduced by batched PTEs population.
>>> The batch size of PTEs population is not allowed to cross:
>>> - page table boundaries
>>> - vma range
>>> - large folio size
>>> - fault_around_bytes
>>
>> I find this patch very interesting. But is it really worth it? Most
>> file-backed page faults are resolved through the ->map_pages() path
>> which is almost always filemap_map_pages(), which does something
>> fairly similar to this already. Do you have any performance numbers?
>>
> I tried the will-it-scale page_fault3:
> https://github.com/antonblanchard/will-it-scale/blob/master/tests/page_fault3.c
> with 96 processes on a test box with 48C/86T.
>
> The test result got about 3.75X better with 4.1X less page fault number
> with this patch.
>
> But It's a micro benchmark which shows extreme friendly case to this patch.
>
> I didn't see observed performance gain with other workloads. I suppose
> shared file write operations may not be common operations? Thanks.
One question I have after reading "which does something fairly similar
to this already", if both paths could be unified.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-01-17 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 16:35 Yin Fengwei
2023-01-13 18:13 ` Matthew Wilcox
2023-01-14 0:58 ` Yin, Fengwei
2023-01-17 9:19 ` Yin, Fengwei
2023-01-17 10:37 ` David Hildenbrand [this message]
2023-01-17 14:46 ` Matthew Wilcox
2023-01-18 1:41 ` Yin, Fengwei
2023-01-18 14:05 ` Yin, Fengwei
2023-01-18 0:58 ` 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=e14b4e9a-612d-fc02-edc0-8f3b6bcf4148@redhat.com \
--to=david@redhat.com \
--cc=dave.hansen@intel.com \
--cc=fengwei.yin@intel.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