From: Miaohe Lin <linmiaohe@huawei.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
Oscar Salvador <osalvador@suse.de>,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH 1/2] mm: Turn folio_test_hugetlb into a PageType
Date: Fri, 15 Mar 2024 14:19:10 +0800 [thread overview]
Message-ID: <a8f92fa8-add4-b992-fd29-ea69175dfeb0@huawei.com> (raw)
In-Reply-To: <ZfMKpiXi_sXAspgr@casper.infradead.org>
On 2024/3/14 22:33, Matthew Wilcox wrote:
> On Thu, Mar 14, 2024 at 11:26:17AM +0100, David Hildenbrand wrote:
>> Should we include this hunk:
>>
>> diff --git a/mm/debug.c b/mm/debug.c
>> index c1c1a6a484e4c..f521e17150a10 100644
>> --- a/mm/debug.c
>> +++ b/mm/debug.c
>> @@ -63,7 +63,8 @@ static void __dump_folio(struct folio *folio, struct page *page,
>> * encode own info, and we must avoid calling page_folio() again.
>> */
>> if (!folio_test_slab(folio)) {
>> - mapcount = atomic_read(&page->_mapcount) + 1;
>> + if (!folio_test_hugetlb(folio))
>> + mapcount = atomic_read(&page->_mapcount) + 1;
>> if (folio_test_large(folio))
>> mapcount += folio_entire_mapcount(folio);
>> }
>>
>> Apart from that, LGTM
>
> I actually want to do a bit more here ...
>
> +++ b/mm/debug.c
> @@ -58,15 +58,10 @@ static void __dump_folio(struct folio *folio, struct page *page,
> int mapcount = 0;
> char *type = "";
>
> - /*
> - * page->_mapcount space in struct page is used by slab pages to
> - * encode own info, and we must avoid calling page_folio() again.
> - */
> - if (!folio_test_slab(folio)) {
> + if (!page_has_type(page)) {
> mapcount = atomic_read(&page->_mapcount) + 1;
> - if (folio_test_large(folio))
> - mapcount += folio_entire_mapcount(folio);
> - }
> + if (folio_test_large(folio))
> + mapcount += folio_entire_mapcount(folio);
Why folio_test_large is not within the "if (!page_has_type(page))" block? I think a slab page could also be large folio.
Or am I miss something?
Thanks.
next prev parent reply other threads:[~2024-03-15 6:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 1:25 [PATCH 0/2] Reliable testing for hugetlb Matthew Wilcox (Oracle)
2024-03-14 1:25 ` [PATCH 1/2] mm: Turn folio_test_hugetlb into a PageType Matthew Wilcox (Oracle)
2024-03-14 10:26 ` David Hildenbrand
2024-03-14 14:33 ` Matthew Wilcox
2024-03-15 6:19 ` Miaohe Lin [this message]
2024-03-15 12:32 ` Matthew Wilcox
2024-03-18 1:45 ` Miaohe Lin
2024-03-14 1:25 ` [PATCH 2/2] mm: Remove a call to compound_head() from is_page_hwpoison() Matthew Wilcox (Oracle)
2024-03-14 10:26 ` David Hildenbrand
2024-03-15 6:38 ` Miaohe Lin
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=a8f92fa8-add4-b992-fd29-ea69175dfeb0@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).