From: "Huang, Ying" <ying.huang@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Longlong Xia <xialonglong1@huawei.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <chenwandun@huawei.com>,
<wangkefeng.wang@huawei.com>, <sunnanyong@huawei.com>
Subject: Re: [PATCH] mm/swapfile: add cond_resched() in get_swap_pages()
Date: Mon, 30 Jan 2023 08:26:41 +0800 [thread overview]
Message-ID: <87wn54c1fi.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <20230129130320.7e2e4445ecc4b172c61c7b9c@linux-foundation.org> (Andrew Morton's message of "Sun, 29 Jan 2023 13:03:20 -0800")
Andrew Morton <akpm@linux-foundation.org> writes:
> On Sat, 28 Jan 2023 09:47:57 +0000 Longlong Xia <xialonglong1@huawei.com> wrote:
>
>> The softlockup still occurs in get_swap_pages() under memory pressure.
>> 64 CPU cores, 64GB memory, and 28 zram devices, the disksize of each
>> zram device is 50MB with same priority as si. Use the stress-ng tool
>> to increase memory pressure, causing the system to oom frequently.
>>
>> The plist_for_each_entry_safe() loops in get_swap_pages() could reach
>> tens of thousands of times to find available space (extreme case:
>> cond_resched() is not called in scan_swap_map_slots()). Let's add
>> cond_resched() into get_swap_pages() when failed to find available
>> space to avoid softlockup.
>>
>> ...
>>
>> --- 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:
>
> This must be pretty rare? My googling for "scan_swap_map of si %d
> failed to find offset" turns up zero reports, but I guess few people
> enable pr_debug.
>
> I wonder if we should remove that pr_debug(). I mean, it's known that
> this happens, what value does the printk add?
Sounds reasonable to me. And if we want to debug, we can use bpf too.
> I'm thinking this fix should be backported into -stable kernels.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2023-01-30 0:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 9:47 Longlong Xia
2023-01-29 0:39 ` Huang, Ying
2023-01-29 21:03 ` Andrew Morton
2023-01-30 0:26 ` Huang, Ying [this message]
2023-01-31 7:10 ` [PATCH -next] mm/swapfile: remove pr_debug " Longlong Xia
2023-01-31 7:27 ` 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=87wn54c1fi.fsf@yhuang6-desk2.ccr.corp.intel.com \
--to=ying.huang@intel.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=xialonglong1@huawei.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