From: Matthew Wilcox <willy@infradead.org>
To: Yang Huan <link@vivo.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
William Kucharski <william.kucharski@oracle.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kernel@vivo.com, Wang Qing <wangqing@vivo.com>
Subject: Re: [PATCH] mm/page_alloc: enable alloc bulk when page owner is on
Date: Fri, 16 Jul 2021 12:22:56 +0100 [thread overview]
Message-ID: <YPFsEDRqWqydcfTY@casper.infradead.org> (raw)
In-Reply-To: <20210716081756.25419-1-link@vivo.com>
On Fri, Jul 16, 2021 at 04:17:53PM +0800, Yang Huan wrote:
> Last alloc bulk version have a bug, when page_owner is on, system maybe
> crashed due to alloc bulk invoke prep_new_page in irq disabled context,
> and set_page_owner use page_flag(may GFP_KERNEL) to get memory and save
> stacktrace.
> We fix it by a circumvention plan -- bandon alloc bulk feature when
> page_owner is set.
> I think both alloc_bulk and page_owner is valuable, so, it's worth to
> find a way enable alloc bulk when page owner is on.
Why do you think it's valuable? The point of alloc_bulk is speed.
Doing the allocation of a stack for each page removes the speed.
Where's the value?
If you're really interested in making both these things work together,
then I observed that all of these pages are going to have the same
allocation stack. Allocating that stack once per call to alloc_bulk,
reference counting it and having each page use the shared stack would
be a good way of combining the two (it'd even save memory!)
This patch, I think, does not make sense.
next prev parent reply other threads:[~2021-07-16 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 8:17 Yang Huan
2021-07-16 11:22 ` Matthew Wilcox [this message]
2021-07-17 1:58 ` 杨欢
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=YPFsEDRqWqydcfTY@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=kernel@vivo.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=link@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wangqing@vivo.com \
--cc=william.kucharski@oracle.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