From: Mel Gorman <mgorman@suse.de>
To: Bharata B Rao <bharata@amd.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, kamezawa.hiroyu@jp.fujitsu.com,
lee.schermerhorn@hp.com, Krupa.Ramakrishnan@amd.com,
Sadagopan.Srinivasan@amd.com
Subject: Re: [FIX PATCH 1/2] mm/page_alloc: Print node fallback order
Date: Mon, 30 Aug 2021 13:26:51 +0100 [thread overview]
Message-ID: <20210830122651.GB4060@suse.de> (raw)
In-Reply-To: <20210830121603.1081-2-bharata@amd.com>
On Mon, Aug 30, 2021 at 05:46:02PM +0530, Bharata B Rao wrote:
> Print information message about the allocation fallback order
> for each NUMA node during boot.
>
> No functional changes here. This makes it easier to illustrate
> the problem in the node fallback list generation, which the
> next patch fixes.
>
> Signed-off-by: Bharata B Rao <bharata@amd.com>
While the message is just informational, I think it's possible that the
bug could have been found earlier if this message was present so...
Acked-by: Mel Gorman <mgorman@suse.de>
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2021-08-30 12:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 12:16 [FIX PATCH 0/2] Fix NUMA nodes fallback list ordering Bharata B Rao
2021-08-30 12:16 ` [FIX PATCH 1/2] mm/page_alloc: Print node fallback order Bharata B Rao
2021-08-30 12:26 ` Mel Gorman [this message]
2021-09-03 4:15 ` Anshuman Khandual
2021-09-03 4:17 ` Bharata B Rao
2021-09-03 4:31 ` Anshuman Khandual
2021-08-30 12:16 ` [FIX PATCH 2/2] mm/page_alloc: Use accumulated load when building node fallback list Bharata B Rao
2021-08-30 12:29 ` Mel Gorman
2021-08-31 9:58 ` Anshuman Khandual
2021-08-31 15:26 ` Ramakrishnan, Krupa
2021-09-03 4:01 ` Anshuman Khandual
2021-09-03 4:20 ` Anshuman Khandual
2021-09-03 4:43 ` Bharata B Rao
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=20210830122651.GB4060@suse.de \
--to=mgorman@suse.de \
--cc=Krupa.Ramakrishnan@amd.com \
--cc=Sadagopan.Srinivasan@amd.com \
--cc=akpm@linux-foundation.org \
--cc=bharata@amd.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.