From: "Yin, Fengwei" <fengwei.yin@intel.com>
To: 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: Sat, 14 Jan 2023 08:58:38 +0800 [thread overview]
Message-ID: <ddd6c9c6-561b-6ba2-521c-bd25a85a1c49@intel.com> (raw)
In-Reply-To: <Y8GfPeQkRRT8kNFU@casper.infradead.org>
On 1/14/2023 2:13 AM, Matthew Wilcox wrote:
> 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?
Yes. The real benefit this patch brings could be very minor. I will try
to get some performance data against this patch. Thanks.
Regards
Yin, Fengwei
next prev parent reply other threads:[~2023-01-14 0:59 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 [this message]
2023-01-17 9:19 ` Yin, Fengwei
2023-01-17 10:37 ` David Hildenbrand
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=ddd6c9c6-561b-6ba2-521c-bd25a85a1c49@intel.com \
--to=fengwei.yin@intel.com \
--cc=dave.hansen@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