From: "Zhang, Qiang" <Qiang.Zhang@windriver.com>
To: Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "mgorman@techsingularity.net" <mgorman@techsingularity.net>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/page_alloc: avoid hard lockups in __alloc_pages_bulk()
Date: Sat, 10 Jul 2021 22:57:53 +0000 [thread overview]
Message-ID: <BL1PR11MB54785E7EA2BFBDAA393F15BBFF179@BL1PR11MB5478.namprd11.prod.outlook.com> (raw)
In-Reply-To: <YOoMq0Bl6M/LV6mJ@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
________________________________
发件人: Matthew Wilcox <willy@infradead.org>
发送时间: 星期日, 七月 11, 2021 05:10
收件人: Andrew Morton
抄送: Zhang, Qiang; mgorman@techsingularity.net; linux-mm@kvack.org; linux-kernel@vger.kernel.org
主题: Re: [PATCH] mm/page_alloc: avoid hard lockups in __alloc_pages_bulk()
[Please note: This e-mail is from an EXTERNAL e-mail address]
On Sat, Jul 10, 2021 at 11:46:13AM -0700, Andrew Morton wrote:
> On Sat, 10 Jul 2021 19:29:29 +0800 qiang.zhang@windriver.com wrote:
>
> > From: Zqiang <qiang.zhang@windriver.com>
> >
> > The __alloc_pages_bulk() mainly used for batch allocation of
> > order-0 pages, in the case of holding pagesets.lock, if too
> > many pages are required, maybe trigger hard lockup watchdog.
>
> Ouch. Has this been observed in testing? If so, can you please share
> the kernel debug output from that event?
>This should be fixed in the caller by asking for fewer pages.
>The NFS and vmalloc cases have already been fixed for this.
The NFS and vmalloc cases haven been fixed？
I don’t see if there is any information about that?
Thanks
Qiang
[-- Attachment #2: Type: text/html, Size: 2214 bytes --]
next prev parent reply other threads:[~2021-07-10 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 11:29 qiang.zhang
2021-07-10 18:46 ` Andrew Morton
2021-07-10 21:10 ` Matthew Wilcox
2021-07-10 22:57 ` Zhang, Qiang [this message]
2021-07-15 8:35 ` Mel Gorman
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=BL1PR11MB54785E7EA2BFBDAA393F15BBFF179@BL1PR11MB5478.namprd11.prod.outlook.com \
--to=qiang.zhang@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=willy@infradead.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