All of lore.kernel.org
 help / color / mirror / Atom feed
From: <pjy@amazon.com>
To: <stable@vger.kernel.org>
Cc: <lmark@codeaurora.org>
Subject: Backport commit 786dee864804 ("mm/memory_hotplug: rate limit page migration warnings")
Date: Fri, 20 Oct 2023 14:01:13 +0000	[thread overview]
Message-ID: <mb61p4jiltmty.fsf@amazon.com> (raw)


Please backport commit 786dee864804 ("mm/memory_hotplug: ratelimit page
migration warnings") to 5.10 stable branch.

Commit message:
"""
When offlining memory the system can attempt to migrate a lot of pages, if
there are problems with migration this can flood the logs.  Printing all
the data hogs the CPU and cause some RT threads to run for a long time,
which may have some bad consequences.

Rate limit the page migration warnings in order to avoid this.
"""

We are sometimes seeing RCU stalls while offlining memory with the 5.10
kernel due to the printing of these messages.

Applying this patch solves the problem by ratelimiting the prints.

Thanks,
Puranjay

             reply	other threads:[~2023-10-20 14:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20 14:01 pjy [this message]
2023-10-20 14:26 ` Backport commit 786dee864804 ("mm/memory_hotplug: rate limit page migration warnings") Greg KH

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=mb61p4jiltmty.fsf@amazon.com \
    --to=pjy@amazon.com \
    --cc=lmark@codeaurora.org \
    --cc=stable@vger.kernel.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.