From: "Yajun Deng" <yajun.deng@linux.dev>
To: "Vlastimil Babka" <vbabka@suse.cz>,
"Andrew Morton" <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Zi Yan" <ziy@nvidia.com>,
"Mel Gorman" <mgorman@techsingularity.net>,
"David Hildenbrand" <david@redhat.com>,
"Mike Rapoport" <rppt@linux.ibm.com>,
"Oscar Salvador" <osalvador@suse.de>
Subject: Re: [PATCH] mm/page_alloc: reduce fallbacks to (MIGRATE_PCPTYPES - 1)
Date: Thu, 09 Feb 2023 02:02:34 +0000 [thread overview]
Message-ID: <cb0292e44321325fbd8c2cc069894f79@linux.dev> (raw)
In-Reply-To: <b95505ab-8206-2a00-e199-e3defecd9d72@suse.cz>
February 9, 2023 12:07 AM, "Vlastimil Babka" <vbabka@suse.cz> wrote:
> On 2/3/23 23:23, Andrew Morton wrote:
>
>> On Fri, 3 Feb 2023 18:01:32 +0800 Yajun Deng <yajun.deng@linux.dev> wrote:
>>
>>> The commit 1dd214b8f21c ("mm: page_alloc: avoid merging non-fallbackable
>>> pageblocks with others") has removed MIGRATE_CMA and MIGRATE_ISOLATE from
>>> fallbacks list. so there is no need to add an element at the end of every
>>> type.
>>>
>>> Reduce fallbacks to (MIGRATE_PCPTYPES - 1).
>
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
>
>> Thanks. `git log' suggests who should be cc'ed when fixing things...
>>
>>> --- a/mm/page_alloc.c
>>> +++ b/mm/page_alloc.c
>>> @@ -2603,10 +2603,10 @@ struct page *__rmqueue_smallest(struct zone *zone, unsigned int order,
>>> *
>>> * The other migratetypes do not have fallbacks.
>>> */
>>> -static int fallbacks[MIGRATE_TYPES][3] = {
>>> - [MIGRATE_UNMOVABLE] = { MIGRATE_RECLAIMABLE, MIGRATE_MOVABLE, MIGRATE_TYPES },
>>> - [MIGRATE_MOVABLE] = { MIGRATE_RECLAIMABLE, MIGRATE_UNMOVABLE, MIGRATE_TYPES },
>>> - [MIGRATE_RECLAIMABLE] = { MIGRATE_UNMOVABLE, MIGRATE_MOVABLE, MIGRATE_TYPES },
>>> +static int fallbacks[MIGRATE_TYPES][MIGRATE_PCPTYPES - 1] = {
>
> Why not also reduce the first index size from [MIGRATE_TYPES] to
> [MIGRATE_PCPTYPES] ?
>
I overlooked this. I'll do it in the next patch.
>>> + [MIGRATE_UNMOVABLE] = { MIGRATE_RECLAIMABLE, MIGRATE_MOVABLE },
>>> + [MIGRATE_MOVABLE] = { MIGRATE_RECLAIMABLE, MIGRATE_UNMOVABLE },
>>> + [MIGRATE_RECLAIMABLE] = { MIGRATE_UNMOVABLE, MIGRATE_MOVABLE },
>>> };
>>>
>>> #ifdef CONFIG_CMA
>>> @@ -2865,11 +2865,8 @@ int find_suitable_fallback(struct free_area *area, unsigned int order,
>>> return -1;
>>>
>>> *can_steal = false;
>>> - for (i = 0;; i++) {
>>> + for (i = 0; i < MIGRATE_PCPTYPES - 1 ; i++) {
>>> fallback_mt = fallbacks[migratetype][i];
>>> - if (fallback_mt == MIGRATE_TYPES)
>>> - break;
>>> -
>>> if (free_area_empty(area, fallback_mt))
>>> continue;
>>>
>>> --
>>> 2.25.1
prev parent reply other threads:[~2023-02-09 2:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 10:01 [PATCH] mm/page_alloc: reduce fallbacks to (MIGRATE_PCPTYPES - 1) Yajun Deng
2023-02-03 22:23 ` Andrew Morton
2023-02-08 16:07 ` Vlastimil Babka
2023-02-09 2:02 ` Yajun Deng [this message]
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=cb0292e44321325fbd8c2cc069894f79@linux.dev \
--to=yajun.deng@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=osalvador@suse.de \
--cc=rppt@linux.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).