From: Xishi Qiu <qiuxishi@huawei.com>
To: Tejun Heo <tj@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Michal Hocko <mhocko@suse.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Linux MM <linux-mm@kvack.org>
Subject: [RFC] can we use vmalloc to alloc thread stack if compaction failed
Date: Thu, 28 Jul 2016 15:08:26 +0800 [thread overview]
Message-ID: <5799AF6A.2070507@huawei.com> (raw)
Usually THREAD_SIZE_ORDER is 2, it means we need to alloc 16kb continuous
physical memory during fork a new process.
If the system's memory is very small, especially the smart phone, maybe there
is only 1G memory. So the free memory is very small and compaction is not
always success in slowpath(__alloc_pages_slowpath), then alloc thread stack
may be failed for memory fragment.
Can we use vmalloc to alloc thread stack if compaction failed in slowpath?
e.g. Use vmalloc as a fallback if alloc_page/kamlloc failed.
I think the performance may be a little regression, and any other problems?
Thanks,
Xishi Qiu
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2016-07-28 7:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 7:08 Xishi Qiu [this message]
2016-07-28 7:20 ` [RFC] can we use vmalloc to alloc thread stack if compaction failed Michal Hocko
2016-07-28 7:41 ` Xishi Qiu
2016-07-28 7:58 ` Michal Hocko
2016-07-28 8:45 ` Xishi Qiu
2016-07-28 9:43 ` Michal Hocko
2016-07-28 10:51 ` Xishi Qiu
2016-07-28 15:07 ` Andy Lutomirski
2016-07-29 3:01 ` Joonsoo Kim
2016-07-29 19:47 ` Andy Lutomirski
2016-08-01 5:30 ` Joonsoo Kim
2016-08-10 11:59 ` Andy Lutomirski
2016-08-16 4:18 ` Joonsoo Kim
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=5799AF6A.2070507@huawei.com \
--to=qiuxishi@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).