From: "Krcka, Tomas" <krckatom@amazon.de>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: Be less noisy during memory hotplug
Date: Wed, 29 Mar 2023 20:46:53 +0000 [thread overview]
Message-ID: <DA14AE2A-0ABA-40A4-A6F7-7279E441ADE7@amazon.com> (raw)
In-Reply-To: <CA+CK2bAPSeEmQk6uazxSn3k7kWf0f6D6z+3BdHdWJPZXFBBg9w@mail.gmail.com>
> On 23. Mar 2023, at 20:06, Pasha Tatashin <pasha.tatashin@soleen.com> wrote:
>
>
> On Thu, Mar 23, 2023 at 2:37 PM Pasha Tatashin
> <pasha.tatashin@soleen.com> wrote:
>>
>> On Thu, Mar 23, 2023 at 1:19 PM Tomas Krcka <krckatom@amazon.de> 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")
>>>
>>> Suggested-by: Jan H. Schönherr <jschoenh@amazon.de>
>>> Signed-off-by: Tomas Krcka <krckatom@amazon.de>
>>
>> Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
>
> Can you please specify what you mean by frequent hotplug: wow frequent
> is it and what is the usecase?
The use case is virtualization environment, case like new virtual machines
are spun up and shut down frequently and where the workload of the virtual
machines varies widely over time. So specially in case of small virtual machines.
We can talk about multiple times per hour, depends on the workload.
>
> Thanks,
> Pasha
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
prev parent reply other threads:[~2023-03-29 20:47 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
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 [this message]
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=DA14AE2A-0ABA-40A4-A6F7-7279E441ADE7@amazon.com \
--to=krckatom@amazon.de \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.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