From: Michal Hocko <mhocko@suse.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
linux-mm@kvack.org, akpm@linux-foundation.org,
n-horiguchi@ah.jp.nec.com, aneesh.kumar@linux.vnet.ibm.com,
gerald.schaefer@de.ibm.com, zhongjiang@huawei.com,
aarcange@redhat.com, kirill.shutemov@linux.intel.com
Subject: Re: [PATCH] mm/hugetlb: Warn the user when issues arise on boot due to hugepages
Date: Wed, 14 Jun 2017 09:27:25 +0200 [thread overview]
Message-ID: <20170614072725.GH6045@dhcp22.suse.cz> (raw)
In-Reply-To: <a855a155-c952-ac6b-04b9-aa7869403c52@oracle.com>
On Tue 13-06-17 09:26:15, Mike Kravetz wrote:
> A thought somewhat related to this discussion:
>
> I noticed that huge pages specified on the kernel command line are allocated
> via 'subsys_initcall'. This is before 'fs_initcall', even though these huge
> pages are only used by hugetlbfs. Was just thinking that it might be better
> to move huge page allocations to later in the init process. At least make
> them part of fs_initcall if not late_initcall?
>
> Only reason for doing this is because huge page allocations are fairly
> tolerant of allocation failure.
I am not really familiar with the initcall hierarchy to be honest. I
even do not understand what relattion does fs_initcall have to
allocation failures. Could you be more specific?
--
Michal Hocko
SUSE Labs
--
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 prev parent reply other threads:[~2017-06-14 7:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 0:54 [PATCH] mm/hugetlb: Warn the user when issues arise on boot due to hugepages Liam R. Howlett
2017-06-05 4:57 ` Michal Hocko
2017-06-05 15:15 ` Liam R. Howlett
2017-06-06 5:49 ` Michal Hocko
2017-06-06 6:01 ` Michal Hocko
2017-06-12 17:28 ` Liam R. Howlett
2017-06-12 17:49 ` Michal Hocko
2017-06-12 18:37 ` Liam R. Howlett
2017-06-12 18:52 ` Michal Hocko
2017-06-13 1:35 ` Liam R. Howlett
2017-06-13 5:42 ` Michal Hocko
2017-06-13 15:25 ` Liam R. Howlett
2017-06-13 16:26 ` Mike Kravetz
2017-06-14 7:27 ` Michal Hocko [this message]
2017-06-14 17:02 ` Mike Kravetz
2017-06-14 7:25 ` Michal Hocko
2017-06-16 19:07 ` Andrew Morton
2017-06-17 0:25 ` Mike Kravetz
2017-06-17 6:51 ` Michal Hocko
2017-06-19 19:59 ` Liam R. Howlett
2017-06-05 22:38 ` Andrew Morton
2017-06-06 19:03 ` Matthew Wilcox
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=20170614072725.GH6045@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=Liam.Howlett@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=zhongjiang@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;
as well as URLs for NNTP newsgroup(s).