From: wangjianxing <wangjianxing@loongson.cn>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
wangjianxing <wangjianxing@loongson.cn>
Subject: [PATCH 1/1] mm/page_alloc: add scheduling point to free_unref_page_list
Date: Tue, 1 Mar 2022 20:38:25 -0500 [thread overview]
Message-ID: <20220302013825.2290315-1-wangjianxing@loongson.cn> (raw)
free a large list of pages maybe cause rcu_sched starved on
non-preemptible kernels
rcu: rcu_sched kthread starved for 5359 jiffies! g454793 f0x0
RCU_GP_WAIT_FQS(5) ->state=0x0 ->cpu=19
[...]
Call Trace:
free_unref_page_list+0x19c/0x270
release_pages+0x3cc/0x498
tlb_flush_mmu_free+0x44/0x70
zap_pte_range+0x450/0x738
unmap_page_range+0x108/0x240
unmap_vmas+0x74/0xf0
unmap_region+0xb0/0x120
do_munmap+0x264/0x438
vm_munmap+0x58/0xa0
sys_munmap+0x10/0x20
syscall_common+0x24/0x38
Signed-off-by: wangjianxing <wangjianxing@loongson.cn>
---
mm/page_alloc.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 3589febc6..1b96421c8 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -3479,6 +3479,9 @@ void free_unref_page_list(struct list_head *list)
*/
if (++batch_count == SWAP_CLUSTER_MAX) {
local_unlock_irqrestore(&pagesets.lock, flags);
+
+ cond_resched();
+
batch_count = 0;
local_lock_irqsave(&pagesets.lock, flags);
}
--
2.27.0
next reply other threads:[~2022-03-02 1:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 1:38 wangjianxing [this message]
2022-03-02 23:34 ` Andrew Morton
2022-03-03 2:02 ` wangjianxing
2022-03-08 16:04 ` Vlastimil Babka
2022-03-08 16:05 ` Vlastimil Babka
2022-03-08 16:19 ` Matthew Wilcox
2022-03-10 1:05 ` Andrew Morton
2022-03-10 2:48 ` wangjianxing
2022-03-10 3:29 ` Andrew Morton
2022-03-10 9:11 ` Vlastimil Babka
2022-03-11 3:22 ` wangjianxing
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=20220302013825.2290315-1-wangjianxing@loongson.cn \
--to=wangjianxing@loongson.cn \
--cc=akpm@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox