From: David Hildenbrand <david@redhat.com>
To: Tomas Krcka <krckatom@amazon.de>, linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pavel Tatashin <pavel.tatashin@microsoft.com>,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Be less noisy during memory hotplug
Date: Thu, 23 Mar 2023 18:27:28 +0100 [thread overview]
Message-ID: <a9985035-237a-467c-6516-f996d56cb7e5@redhat.com> (raw)
In-Reply-To: <20230323171904.14444-1-krckatom@amazon.de>
On 23.03.23 18:19, Tomas Krcka wrote:
> Turn a pr_info() into a pr_debug() to prevent dmesg spamming on systems
> where memory hotplug is a frequent operation.
>
> Fixes: 966cf44f637e ("mm: defer ZONE_DEVICE page initialization to the point where we init pgmap")
>
Fixes? I suggest top drop that tag here.
> Suggested-by: Jan H. Schönherr <jschoenh@amazon.de>
> Signed-off-by: Tomas Krcka <krckatom@amazon.de>
> ---
> mm/page_alloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index ac1fc986af44..14d70f4e6c0a 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -6959,7 +6959,7 @@ void __ref memmap_init_zone_device(struct zone *zone,
> compound_nr_pages(altmap, pfns_per_compound));
> }
>
> - pr_info("%s initialised %lu pages in %ums\n", __func__,
> + pr_debug("%s initialised %lu pages in %ums\n", __func__,
> nr_pages, jiffies_to_msecs(jiffies - start));
> }
>
Acked-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-03-23 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 17:19 Tomas Krcka
2023-03-23 17:27 ` David Hildenbrand [this message]
2023-03-23 17:43 ` [PATCH v2] " Tomas Krcka
2023-03-23 18:37 ` [PATCH] " Pasha Tatashin
2023-03-23 19:06 ` Pasha Tatashin
2023-03-29 20:46 ` Krcka, Tomas
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=a9985035-237a-467c-6516-f996d56cb7e5@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=krckatom@amazon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pavel.tatashin@microsoft.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