From: "Huang, Ying" <ying.huang@intel.com>
To: Barry Song <21cnbao@gmail.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
david@redhat.com, willy@infradead.org, ryan.roberts@arm.com,
yosryahmed@google.com, hughd@google.com, hannes@cmpxchg.org,
surenb@google.com, xiang@kernel.org, yuzhao@google.com,
chrisl@kernel.org, kasong@tencent.com, ziy@nvidia.com,
baolin.wang@linux.alibaba.com, hanchuanhua@oppo.com,
Barry Song <v-songbaohua@oppo.com>
Subject: Re: [PATCH 4/4] mm: swap: entirely map large folios found in swapcache
Date: Mon, 08 Apr 2024 15:18:11 +0800 [thread overview]
Message-ID: <87wmp88gr0.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <20240402073237.240995-5-21cnbao@gmail.com> (Barry Song's message of "Tue, 2 Apr 2024 20:32:37 +1300")
Barry Song <21cnbao@gmail.com> writes:
> From: Chuanhua Han <hanchuanhua@oppo.com>
>
> When a large folio is found in the swapcache, the current implementation
> requires calling do_swap_page() nr_pages times, resulting in nr_pages
> page faults. This patch opts to map the entire large folio at once to
> minimize page faults. Additionally, redundant checks and early exits
> for ARM64 MTE restoring are removed.
For large folios in reclaiming, it makes sense to restore all PTE
mappings to the large folio to reduce the number of page faults.
But for large folios swapped in, I think that it's better to map one PTE
which triggers the page fault only. Because this makes us get the
opportunity to trap the page accesses to the sub-pages of the large
folio that is swapped in ahead (kind of swap readahead). Then we can
decide the order of large folio swapin based on the readahead window
information. That is, we may need to check PageReadahead() to decide
whether to map all PTEs in the future.
--
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2024-04-08 7:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 7:32 [PATCH 0/4] large folios swap-in: handle refault cases first Barry Song
2024-04-02 7:32 ` [PATCH 1/4] mm: swap: introduce swap_free_nr() for batched swap_free() Barry Song
2024-04-02 7:32 ` [PATCH 2/4] mm: swap: make should_try_to_free_swap() support large-folio Barry Song
2024-04-02 7:32 ` [PATCH 3/4] mm: swap_pte_batch: add an output argument to reture if all swap entries are exclusive Barry Song
2024-04-02 7:32 ` [PATCH 4/4] mm: swap: entirely map large folios found in swapcache Barry Song
2024-04-07 2:24 ` Barry Song
2024-04-08 7:18 ` Huang, Ying [this message]
2024-04-08 7:27 ` Barry Song
2024-04-08 7:49 ` Huang, Ying
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=87wmp88gr0.fsf@yhuang6-desk2.ccr.corp.intel.com \
--to=ying.huang@intel.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=chrisl@kernel.org \
--cc=david@redhat.com \
--cc=hanchuanhua@oppo.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kasong@tencent.com \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=surenb@google.com \
--cc=v-songbaohua@oppo.com \
--cc=willy@infradead.org \
--cc=xiang@kernel.org \
--cc=yosryahmed@google.com \
--cc=yuzhao@google.com \
--cc=ziy@nvidia.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