From: David Hildenbrand <david@redhat.com>
To: liuq <liuq131@chinatelecom.cn>, akpm@linux-foundation.org
Cc: ying.huang@intel.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm/min_free_kbytes: modify min_free_kbytes calculation rules
Date: Wed, 21 Jun 2023 13:18:00 +0200 [thread overview]
Message-ID: <95531f88-a1bd-3347-dc60-8e16de811145@redhat.com> (raw)
In-Reply-To: <20230621073912.21747-1-liuq131@chinatelecom.cn>
On 21.06.23 09:39, liuq wrote:
> The current calculation of min_free_kbytes only uses ZONE_DMA and
> ZONE_NORMAL pages,but the ZONE_MOVABLE zone->_watermark[WMARK_MIN]
> will also divide part of min_free_kbytes.This will cause the min
> watermark of ZONE_NORMAL to be too small in the presence of ZONE_MOVEABLE.
>
> __GFP_HIGH and PF_MEMALLOC allocations usually don't need moveable
> zone pages, so just like ZONE_HIGHMEM, cap pages_min to a small
> value in __setup_per_zone_wmarks.
>
> Signed-off-by: liuq <liuq131@chinatelecom.cn>
> ---
> mm/page_alloc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 47421bedc12b..608384712a89 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -6364,7 +6364,7 @@ static void __setup_per_zone_wmarks(void)
>
> /* Calculate total number of !ZONE_HIGHMEM pages */
> for_each_zone(zone) {
> - if (!is_highmem(zone))
> + if (!is_highmem(zone) || zone_idx(zone) != ZONE_MOVABLE)
> lowmem_pages += zone_managed_pages(zone);
> }
>
> @@ -6374,7 +6374,7 @@ static void __setup_per_zone_wmarks(void)
> spin_lock_irqsave(&zone->lock, flags);
> tmp = (u64)pages_min * zone_managed_pages(zone);
> do_div(tmp, lowmem_pages);
> - if (is_highmem(zone)) {
> + if (is_highmem(zone) || zone_idx(zone) == ZONE_MOVABLE) {
> /*
> * __GFP_HIGH and PF_MEMALLOC allocations usually don't
> * need highmem pages, so cap pages_min to a small
Patch subject should probably be something like
"mm/page_alloc: fix min_free_kbytes calculation regarding ZONE_MOVABLE"
?
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-06-21 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 7:39 liuq
2023-06-21 7:45 ` Huang, Ying
2023-06-21 11:18 ` David Hildenbrand [this message]
[not found] <30f4ac69-fb51-8414-fdaf-a1366a84bbd3@chinatelecom.cn>
2023-06-21 8:17 ` liuq
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=95531f88-a1bd-3347-dc60-8e16de811145@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuq131@chinatelecom.cn \
--cc=ying.huang@intel.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