From: David Hildenbrand <david@redhat.com>
To: Barry Song <21cnbao@gmail.com>,
akpm@linux-foundation.org, linux-mm@kvack.org
Cc: chrisl@kernel.org, linux-kernel@vger.kernel.org, mhocko@suse.com,
ryan.roberts@arm.com, baolin.wang@linux.alibaba.com,
yosryahmed@google.com, shy828301@gmail.com, surenb@google.com,
v-songbaohua@oppo.com, willy@infradead.org, ying.huang@intel.com,
yuzhao@google.com
Subject: Re: [PATCH RFC 2/3] mm: do_swap_page: use folio_add_new_anon_rmap() if folio_test_anon(folio)==false
Date: Thu, 13 Jun 2024 11:23:27 +0200 [thread overview]
Message-ID: <77da1feb-2257-4545-9427-5729250ceb2b@redhat.com> (raw)
In-Reply-To: <20240613000721.23093-3-21cnbao@gmail.com>
On 13.06.24 02:07, Barry Song wrote:
> From: Barry Song <v-songbaohua@oppo.com>
>
> For the !folio_test_anon(folio) case, we can now invoke folio_add_new_anon_rmap()
> with the rmap flags set to either EXCLUSIVE or non-EXCLUSIVE. This action will
> suppress the VM_WARN_ON_FOLIO check within __folio_add_anon_rmap() while initiating
> the process of bringing up mTHP swapin.
>
> static __always_inline void __folio_add_anon_rmap(struct folio *folio,
> struct page *page, int nr_pages, struct vm_area_struct *vma,
> unsigned long address, rmap_t flags, enum rmap_level level)
> {
> ...
> if (unlikely(!folio_test_anon(folio))) {
> VM_WARN_ON_FOLIO(folio_test_large(folio) &&
> level != RMAP_LEVEL_PMD, folio);
> }
> ...
> }
>
> It also enhances the code’s readability.
>
> Suggested-by: David Hildenbrand <david@redhat.com>
> Signed-off-by: Barry Song <v-songbaohua@oppo.com>
> ---
> mm/memory.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/memory.c b/mm/memory.c
> index 2f94921091fb..9c962f62f928 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -4339,6 +4339,8 @@ vm_fault_t do_swap_page(struct vm_fault *vmf)
> if (unlikely(folio != swapcache && swapcache)) {
> folio_add_new_anon_rmap(folio, vma, address, RMAP_EXCLUSIVE);
> folio_add_lru_vma(folio, vma);
> + } else if (!folio_test_anon(folio)) {
> + folio_add_new_anon_rmap(folio, vma, address, rmap_flags);
So, with large folio swapin, we would never end up here if any swp PTE
is !exclusive, because we would make sure to allocate a large folio only
for suitable regions, correct?
It can certainly happen during swapout + refault with large folios. But
there, we will always have folio_test_anon() still set and wouldn't run
into this code path.
(it will all be better with per-folio PAE bit, but that will take some
more time until I actually get to implement it properly, handling all
the nasty corner cases)
Better add a comment regarding why we are sure that the complete thing
is exclusive (e.g., currently only small folios).
> } else {
> folio_add_anon_rmap_ptes(folio, page, nr_pages, vma, address,
> rmap_flags);
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-06-13 9:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 0:07 [PATCH RFC 0/3] mm: clarify folio_add_new_anon_rmap() and __folio_add_anon_rmap() Barry Song
2024-06-13 0:07 ` [PATCH RFC 1/3] mm: extend rmap flags arguments for folio_add_new_anon_rmap Barry Song
2024-06-13 8:39 ` Barry Song
2024-06-13 0:07 ` [PATCH RFC 2/3] mm: do_swap_page: use folio_add_new_anon_rmap() if folio_test_anon(folio)==false Barry Song
2024-06-13 9:23 ` David Hildenbrand [this message]
2024-06-13 9:58 ` Barry Song
2024-06-13 10:37 ` David Hildenbrand
2024-06-13 10:55 ` Barry Song
2024-06-13 0:07 ` [PATCH RFC 3/3] mm: remove folio_test_anon(folio)==false path in __folio_add_anon_rmap() Barry Song
2024-06-13 8:46 ` Barry Song
2024-06-13 8:49 ` David Hildenbrand
2024-06-13 9:06 ` Barry Song
2024-06-13 9:12 ` David Hildenbrand
2024-06-14 7:56 ` Barry Song
2024-06-14 8:51 ` David Hildenbrand
2024-06-14 8:56 ` Barry Song
2024-06-14 8:58 ` Barry Song
2024-06-14 9:04 ` David Hildenbrand
2024-06-14 9:33 ` Barry Song
2024-06-14 11:10 ` David Hildenbrand
2024-06-14 22:24 ` Barry Song
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=77da1feb-2257-4545-9427-5729250ceb2b@redhat.com \
--to=david@redhat.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=chrisl@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=surenb@google.com \
--cc=v-songbaohua@oppo.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--cc=yosryahmed@google.com \
--cc=yuzhao@google.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