linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Huanpeng Xin <xinhuanpeng9@gmail.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	xinhuanpeng <xinhuanpeng@xiaomi.com>
Subject: Re: [PATCH] mm: add a new emergency page migratetype.
Date: Tue, 7 Jun 2022 14:55:05 +0200	[thread overview]
Message-ID: <fc866097-f529-158e-8f24-5d42b11d28b1@redhat.com> (raw)
In-Reply-To: <20220606032709.11800-1-xinhuanpeng9@gmail.com>

On 06.06.22 05:27, Huanpeng Xin wrote:
> From: xinhuanpeng <xinhuanpeng@xiaomi.com>
> 
> add a new page migratetype reserved for
> non-costly non-NOWARN page allocation failure.

Sorry to say, but this patch description is not expressive enough. I
have absolutely no clue what you are trying to achieve and why we should
care.

Especially, why do we care about locally grouping these allocations
(that's what pageblock flags are for after all)?

Your Kconfig option is also not particularly user friendly to read either:

"This enables the migration type MIGRATE_EMERGENCY,which reserves
 a small amount of memory for non-costly non-NOWARN page allocation
 failure."

Usually we reserve memory via different mechanisms, like atomic
reserves? Why can't something like that be used.

On first sight, defining a new pageblock migratype feels wrong to me.
But then, I have no clue what you are actually trying to achieve.

-- 
Thanks,

David / dhildenb



  reply	other threads:[~2022-06-07 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06  3:27 Huanpeng Xin
2022-06-07 12:55 ` David Hildenbrand [this message]
2022-06-09  2:36   ` xin huanpeng
2022-06-12 11:57 ` 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=fc866097-f529-158e-8f24-5d42b11d28b1@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=xinhuanpeng9@gmail.com \
    --cc=xinhuanpeng@xiaomi.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