From: Michal Hocko <mhocko@kernel.org>
To: Guilherme Piccoli <gpiccoli@canonical.com>
Cc: Qian Cai <cai@lca.pw>,
linux-mm@kvack.org, mike.kravetz@oracle.com,
linux-kernel@vger.kernel.org,
Jay Vosburgh <jay.vosburgh@canonical.com>,
"Guilherme G. Piccoli" <kernel@gpiccoli.net>
Subject: Re: [PATCH] hugetlb: Add nohugepages parameter to prevent hugepages creation
Date: Tue, 15 Oct 2019 14:18:03 +0200 [thread overview]
Message-ID: <20191015121803.GB24932@dhcp22.suse.cz> (raw)
In-Reply-To: <CAHD1Q_x+m0ZT_xfLV3j6ma3Cc88fk9KnoS4yytS=PHBvJN7nnQ@mail.gmail.com>
On Fri 11-10-19 21:41:01, Guilherme Piccoli wrote:
> On Fri, Oct 11, 2019 at 8:52 PM Qian Cai <cai@lca.pw> wrote:
> >
> >
> > It simply error-prone to reuse the sysctl.conf from the first kernel, as it could contains lots of things that will kill kdump kernel.
>
> Makes sense, I agree with you. But still, there's no
> formal/right/single way to do kdump, so I don't think we should rely
> on "rootfs kdump is wrong" to refuse this patch's idea. If so, we
> should then formalize the right way of kdumping.
> Of course, this is only my opinion, let's see what people think about it!
I do agree with Qian Cai here. Kdump kernel requires a very tailored
environment considering it is running in a very restricted
configuration. The hugetlb pre-allocation sounds like a tooling problem
and should be fixed at that layer.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-10-15 12:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 22:39 Guilherme G. Piccoli
2019-10-11 23:35 ` Qian Cai
2019-10-11 23:41 ` Guilherme Piccoli
2019-10-11 23:52 ` Qian Cai
2019-10-12 0:41 ` Guilherme Piccoli
2019-10-15 12:18 ` Michal Hocko [this message]
2019-10-15 13:58 ` Guilherme G. Piccoli
2019-10-15 14:05 ` Michal Hocko
2019-10-15 14:09 ` Guilherme G. Piccoli
2019-10-18 18:29 ` Mike Kravetz
2019-10-24 16:21 ` Guilherme G. Piccoli
2019-10-14 18:25 ` Mike Kravetz
2019-10-15 4:50 ` Guilherme G. Piccoli
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=20191015121803.GB24932@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=cai@lca.pw \
--cc=gpiccoli@canonical.com \
--cc=jay.vosburgh@canonical.com \
--cc=kernel@gpiccoli.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@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