From: Rong Qianfeng <11065417@vivo.com>
To: David Hildenbrand <david@redhat.com>
Cc: opensource.kernel@vivo.com, Rong Qianfeng <rongqianfeng@vivo.com>,
vbabka@suse.cz, mgorman@techsingularity.net,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Skip the reserved bootmem for compaction
Date: Tue, 3 Sep 2024 15:14:11 +0800 [thread overview]
Message-ID: <c4ec57e5-49e1-413f-a1e2-e258c628c55f@vivo.com> (raw)
In-Reply-To: <3b8994a6-cbe5-46be-86eb-b78198c31ef8@redhat.com>
Hi David,
Thanks very much for the detailed comments and explanations!
在 2024/9/2 21:45, David Hildenbrand 写道:
> On 02.09.24 14:24, Rong Qianfeng wrote:
>> Reserved pages are basically non-lru pages. This kind of memory can't be
>> used as migration sources and targets, skip it can bring some
>> performance
>> benefits.
>
> Any numbers? :)
I am still thinking about how to design test cases. If you have any good
suggestions, please tell me. Thank you very much.
>> +
>> +extern void set_pageblock_skip_range(unsigned long start_pfn,
>> + unsigned long end_pfn);
>
> two tabs indentation on the second line please. Applies to all others as
> well.
Got it. Will do in the next version.
>>
>> + /*
>> + * We set the PB_migrate_skip in
>> + * reserve_bootmem_region() for cma
>> + * memory, clear it now.
>
> You can fit this easily into less lines
Will do in the next version. Thanks.
>>
>> + /*
>> + * Clear PB_migrate_skip if the memory have released
>> + * to the buddy system.
>> + */
>
> ... after freeing the memory to the buddy."
>
> And maybe
>
> if (pages) {
> if (s)
> pr_info("Freeing %s memory: %ldK\n", s, K(pages));
> clear_pageblock_skip_range(...)
> }
>
>> + clear_pageblock_skip_range(page_to_pfn(virt_to_page(start)),
>> + page_to_pfn(virt_to_page(end)));
>> +
>
> PHYS_PFN(virt_to_phys(start)) might look a bit nicer, not need to
> get pages involved. virt_to_pfn might be even better(), but it's
> not available on all archs I think.
You are right, I tried to use virt_to_pfn, but later found out that it
is not
supported on x86.
>
>
> What about free_reserved_page() ? There might be more, though
> (kimage_free_pages()). You have to take a look at all functions where we
> clear PageReserved.
Thanks for your reminder, I found that I missed a lot of functions.
Maybe a better choice is to clear PB_migrate_skip in free_reserved_page()
to reduce the amount of modification.
Best Regards,
Qianfeng
next prev parent reply other threads:[~2024-09-03 7:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 12:24 Rong Qianfeng
2024-09-02 13:45 ` David Hildenbrand
2024-09-03 7:14 ` Rong Qianfeng [this message]
2024-09-03 9:56 ` David Hildenbrand
2024-09-04 11:13 ` Mel Gorman
2024-09-04 11:59 ` Rong Qianfeng
2024-09-04 15:38 ` Mike Rapoport
2024-09-05 3:10 ` Rong Qianfeng
2024-09-04 14:54 ` kernel test robot
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=c4ec57e5-49e1-413f-a1e2-e258c628c55f@vivo.com \
--to=11065417@vivo.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=opensource.kernel@vivo.com \
--cc=rongqianfeng@vivo.com \
--cc=rppt@kernel.org \
--cc=vbabka@suse.cz \
--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