From: Longlong Xia <xialonglong1@huawei.com>
To: <akpm@linux-foundation.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<ying.huang@intel.com>, <chenwandun@huawei.com>,
<wangkefeng.wang@huawei.com>, <sunnanyong@huawei.com>,
Longlong Xia <xialonglong1@huawei.com>
Subject: [RFC PATCH] mm/swapfile: add cond_resched() in get_swap_pages()
Date: Sat, 28 Jan 2023 07:20:14 +0000 [thread overview]
Message-ID: <20230128072014.1030445-1-xialonglong1@huawei.com> (raw)
We found that the plist_for_each_entry_safe() loop in get_swap_pages()
could reach tens of thousands of times to find available space (extreme
case: cond_resched() is not called in the loop). The test scenario is like
commit de1ccfb64824 ("swapfile: fix soft lockup in scan_swap_map_slots")
does. On the other hand, scan_swap_map_slots() needs to reach LATENCY_LIMIT
before calling cond_resched(), so cond_resched() is needed when failed to
find available space to avoid softlockup.
Signed-off-by: Longlong Xia <xialonglong1@huawei.com>
---
mm/swapfile.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/mm/swapfile.c b/mm/swapfile.c
index 908a529bca12..4fa440e87cd6 100644
--- a/mm/swapfile.c
+++ b/mm/swapfile.c
@@ -1100,6 +1100,7 @@ int get_swap_pages(int n_goal, swp_entry_t swp_entries[], int entry_size)
goto check_out;
pr_debug("scan_swap_map of si %d failed to find offset\n",
si->type);
+ cond_resched();
spin_lock(&swap_avail_lock);
nextsi:
--
2.25.1
next reply other threads:[~2023-01-28 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 7:20 Longlong Xia [this message]
2023-01-28 8:29 ` Huang, Ying
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=20230128072014.1030445-1-xialonglong1@huawei.com \
--to=xialonglong1@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=chenwandun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sunnanyong@huawei.com \
--cc=wangkefeng.wang@huawei.com \
--cc=ying.huang@intel.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