From: Qi Zheng <zhengqi.arch@bytedance.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: mike.kravetz@oracle.com, songmuchun@bytedance.com,
akpm@linux-foundation.org, catalin.marinas@arm.com,
will@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: hugetlb: kill set_huge_swap_pte_at()
Date: Tue, 28 Jun 2022 11:34:29 +0800 [thread overview]
Message-ID: <f3d8aabe-3d02-8851-b5e9-b0dcdb7c0b6e@bytedance.com> (raw)
In-Reply-To: <YrnBm9FGizF1iLsW@casper.infradead.org>
On 2022/6/27 22:41, Matthew Wilcox wrote:
> On Sun, Jun 26, 2022 at 10:57:17PM +0800, Qi Zheng wrote:
>> The commit e5251fd43007 ("mm/hugetlb: introduce set_huge_swap_pte_at()
>> helper") add set_huge_swap_pte_at() to handle swap entries on
>> architectures that support hugepages consisting of contiguous ptes.
>> And currently the set_huge_swap_pte_at() is only overridden by arm64.
>
> Bleh. I hate the way we handle these currently.
>
>> +static inline struct folio *hugetlb_swap_entry_to_folio(swp_entry_t entry)
>> +{
>> + VM_BUG_ON(!is_migration_entry(entry) && !is_hwpoison_entry(entry));
>> +
>> + return page_folio(pfn_to_page(swp_offset(entry)));
>> +}
>
> We haven't needed a pfn_to_folio() yet, but perhaps we should have one?
Hi,
IMO, it would be better to have a pfn_to_folio(), which can save the
redundant page_folio() call in the current case.
But this is not related to the current patch, maybe it can be a
separate optimization patch.
>
> Related, how should we store migration entries for multi-order folios
> in the page tables? We can either encode the individual page in
> question, or we can encode the folio. Do we need to support folios
> being mapped askew (ie unaligned), or will folios always be mapped
> aligned?
Do we currently have a scenario where we need to use skew mapped folios?
Maybe it can be used in pte-mapped THP? Hmm, I have no idea.
>
>> + if (!pte_present(pte)) {
>> + struct folio *folio;
>> +
>> + folio = hugetlb_swap_entry_to_folio(pte_to_swp_entry(pte));
>> + ncontig = num_contig_ptes(folio_size(folio), &pgsize);
>> +
>> + for (i = 0; i < ncontig; i++, ptep++)
>> + set_pte_at(mm, addr, ptep, pte);
>> + return;
>> + }
>
> It seems like a shame to calculate folio_size() only to turn it into a
> number of pages. Don't you want to just use:
>
> ncontig = folio_nr_pages(folio);
We can't use folio_nr_pages() here, because for PMD_SIZE we only need
one entry instead of the PTRS_PER_PTE entries returned by
folio_nr_pages().
Thanks,
Qi
>
--
Thanks,
Qi
next prev parent reply other threads:[~2022-06-28 3:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 14:57 Qi Zheng
2022-06-27 3:32 ` Muchun Song
2022-06-27 6:18 ` Anshuman Khandual
2022-06-27 6:55 ` Qi Zheng
2022-06-27 7:14 ` Anshuman Khandual
2022-06-27 7:29 ` Qi Zheng
2022-06-27 7:35 ` Anshuman Khandual
2022-06-27 14:34 ` Matthew Wilcox
2022-06-28 5:47 ` Anshuman Khandual
2022-06-27 7:44 ` Muchun Song
2022-06-27 14:41 ` Matthew Wilcox
2022-06-28 3:34 ` Qi Zheng [this message]
2023-09-21 16:25 ` Ryan Roberts
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=f3d8aabe-3d02-8851-b5e9-b0dcdb7c0b6e@bytedance.com \
--to=zhengqi.arch@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=songmuchun@bytedance.com \
--cc=will@kernel.org \
--cc=willy@infradead.org \
/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