From: David Rientjes <rientjes@google.com>
To: Charan Teja Reddy <charante@codeaurora.org>
Cc: akpm@linux-foundation.org, vbabka@suse.cz, mhocko@suse.com,
vinmenon@codeaurora.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: page_alloc: update the COMPACT[STALL|FAIL] events properly
Date: Mon, 1 Feb 2021 13:24:49 -0800 (PST) [thread overview]
Message-ID: <d9d1dd7b-1fe7-67b6-6ba4-fb1a6faa8fae@google.com> (raw)
In-Reply-To: <1612187338-19100-1-git-send-email-charante@codeaurora.org>
On Mon, 1 Feb 2021, Charan Teja Reddy wrote:
> By defination, COMPACT[STALL|FAIL] events needs to be counted when there
s/defination/definition/
> is 'At least in one zone compaction wasn't deferred or skipped from the
> direct compaction'. And when compaction is skipped or deferred,
> COMPACT_SKIPPED will be returned but it will still go and update these
> compaction events which is wrong in the sense that COMPACT[STALL|FAIL]
> is counted without even trying the compaction.
>
> Correct this by skipping the counting of these events when
> COMPACT_SKIPPED is returned for compaction. This indirectly also avoid
> the unnecessary try into the get_page_from_freelist() when compaction is
> not even tried.
>
> Signed-off-by: Charan Teja Reddy <charante@codeaurora.org>
> ---
> mm/page_alloc.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 519a60d..531f244 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -4152,6 +4152,8 @@ __alloc_pages_direct_compact(gfp_t gfp_mask, unsigned int order,
> memalloc_noreclaim_restore(noreclaim_flag);
> psi_memstall_leave(&pflags);
>
> + if (*compact_result == COMPACT_SKIPPED)
> + return NULL;
> /*
> * At least in one zone compaction wasn't deferred or skipped, so let's
> * count a compaction stall
This makes sense, I wonder if it would also be useful to check that
page == NULL, either in try_to_compact_pages() or here for
COMPACT_SKIPPED?
next prev parent reply other threads:[~2021-02-01 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 13:48 Charan Teja Reddy
2021-02-01 21:24 ` David Rientjes [this message]
2021-02-02 12:49 ` Charan Teja Kalla
2021-02-05 22:28 ` David Rientjes
2021-02-06 1:57 ` Charan Teja Kalla
2021-02-09 16:08 ` Vlastimil Babka
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=d9d1dd7b-1fe7-67b6-6ba4-fb1a6faa8fae@google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=charante@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
--cc=vinmenon@codeaurora.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