From: David Hildenbrand <david@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Muchun Song <muchun.song@linux.dev>
Subject: Re: [PATCH v1 6/6] mm/hugetlb: use folio->lru int demote_free_hugetlb_folios()
Date: Fri, 10 Jan 2025 20:32:52 +0100 [thread overview]
Message-ID: <542e2241-33ff-4ebd-9ee7-d95413d2ad1e@redhat.com> (raw)
In-Reply-To: <Z4FuA-OJkygYTOT6@casper.infradead.org>
On 10.01.25 19:59, Matthew Wilcox wrote:
> On Fri, Jan 10, 2025 at 07:21:49PM +0100, David Hildenbrand wrote:
>> We are demoting hugetlb folios to smaller hugetlb folios; let's avoid
>> messing with pages where avoidable.
>>
>> Signed-off-by: David Hildenbrand <david@redhat.com>
>
> Good stuff. I have questions.
>
>> +++ b/mm/hugetlb.c
>> @@ -3822,13 +3822,15 @@ static long demote_free_hugetlb_folios(struct hstate *src, struct hstate *dst,
>>
>> for (i = 0; i < pages_per_huge_page(src); i += pages_per_huge_page(dst)) {
>> struct page *page = folio_page(folio, i);
>> + struct folio *new_folio;
>
> I'm usually very against casting from page to folio, but I think it
> might be the better option in this case ...
>
>> page->mapping = NULL;
>
> because then we could do new_folio->mapping = NULL.
>
> We're going to have to do serious changes to this function anyway to
> convert from Ottawa to the New York interpretation, so the cast doesn't
> give me the feeling of danger that it would elsewhere.
Hm, that makes me wonder if we should do it even more similar like our
other split function (__split_huge_page_tail)?
diff --git a/mm/hugetlb.c b/mm/hugetlb.c
index 60617eecb99dd..23fe5654f632c 100644
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -3821,14 +3821,18 @@ static long demote_free_hugetlb_folios(struct hstate *src, struct hstate *dst,
pgalloc_tag_split(folio, huge_page_order(src), huge_page_order(dst));
for (i = 0; i < pages_per_huge_page(src); i += pages_per_huge_page(dst)) {
struct page *page = folio_page(folio, i);
+ /* Careful: see __split_huge_page_tail() */
+ struct folio *new_folio = (struct folio *)page;
- page->mapping = NULL;
clear_compound_head(page);
prep_compound_page(page, dst->order);
- init_new_hugetlb_folio(dst, page_folio(page));
- list_add(&page->lru, &dst_list);
+ new_folio->mapping = NULL;
+ init_new_hugetlb_folio(dst, new_folio);
+ list_add(&new_folio->lru, &dst_list);
}
}
I was even wondering if we should be using nth_page() instead of folio_page() --
similar to __split_huge_page_tail.
If we'd add sanity checking in current code to folio_page() to verify that i
falls inside the folio, the current code would blow up as we modify the
folio using prep_compound_page().
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-01-10 19:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 18:21 [PATCH v1 0/6] mm/hugetlb: folio and migration cleanups David Hildenbrand
2025-01-10 18:21 ` [PATCH v1 1/6] mm/huge_memory: convert has_hwpoisoned into a pure folio flag David Hildenbrand
2025-01-10 18:39 ` Matthew Wilcox
2025-01-10 18:21 ` [PATCH v1 2/6] mm/hugetlb: rename isolate_hugetlb() to folio_isolate_hugetlb() David Hildenbrand
2025-01-10 18:41 ` Matthew Wilcox
2025-01-13 12:25 ` Baolin Wang
2025-01-10 18:21 ` [PATCH v1 3/6] mm/migrate: don't call folio_putback_active_hugetlb() on dst hugetlb folio David Hildenbrand
2025-01-13 7:00 ` Baolin Wang
2025-01-13 9:50 ` David Hildenbrand
2025-01-13 12:21 ` Baolin Wang
2025-01-13 12:26 ` David Hildenbrand
2025-01-10 18:21 ` [PATCH v1 4/6] mm/hugetlb: rename folio_putback_active_hugetlb() to folio_putback_hugetlb() David Hildenbrand
2025-01-13 12:27 ` Baolin Wang
2025-01-10 18:21 ` [PATCH v1 5/6] mm/hugetlb-cgroup: convert hugetlb_cgroup_css_offline() to work on folios David Hildenbrand
2025-01-10 18:45 ` Matthew Wilcox
2025-01-10 18:21 ` [PATCH v1 6/6] mm/hugetlb: use folio->lru int demote_free_hugetlb_folios() David Hildenbrand
2025-01-10 18:59 ` Matthew Wilcox
2025-01-10 19:32 ` David Hildenbrand [this message]
2025-01-10 18:23 ` [PATCH v1 0/6] mm/hugetlb: folio and migration cleanups David Hildenbrand
2025-01-10 18:59 ` Matthew Wilcox
2025-01-10 19:17 ` David Hildenbrand
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=542e2241-33ff-4ebd-9ee7-d95413d2ad1e@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--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