From: Vlastimil Babka <vbabka@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>,
wangjianxing <wangjianxing@loongson.cn>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Michal Hocko <mhocko@suse.com>,
Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [PATCH 1/1] mm/page_alloc: add scheduling point to free_unref_page_list
Date: Tue, 8 Mar 2022 17:04:59 +0100 [thread overview]
Message-ID: <aab854b3-d9fd-3454-c06b-01ff441dec08@suse.cz> (raw)
In-Reply-To: <20220302153433.719caef31bd9e99319c5e6a2@linux-foundation.org>
On 3/3/22 00:34, Andrew Morton wrote:
> On Tue, 1 Mar 2022 20:38:25 -0500 wangjianxing <wangjianxing@loongson.cn> wrote:
>
>> 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
>
> Thanks.
>
> How did this large list of pages come about?
Looks like it came from TLB batching. But I got lost in the maze of it
trying to figure out how large the batch can grow.
> Will people be seeing this message in upstream kernels, or is it
> specific to some caller code which you have added?
>
> Please always include details such as this so that others can determine
> whether the fix should be backported into -stable kernels.
>
>
next prev parent reply other threads:[~2022-03-08 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 1:38 wangjianxing
2022-03-02 23:34 ` Andrew Morton
2022-03-03 2:02 ` wangjianxing
2022-03-08 16:04 ` Vlastimil Babka [this message]
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=aab854b3-d9fd-3454-c06b-01ff441dec08@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=wangjianxing@loongson.cn \
/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