From: Baoquan He <bhe@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: mhocko@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, akpm@linux-foundation.org, corbet@lwn.net,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] mm/page_alloc: Deprecate kernelcore=nn and movable_core=
Date: Wed, 18 Jul 2018 07:31:00 +0800 [thread overview]
Message-ID: <20180717233100.GH1724@MiWiFi-R3L-srv> (raw)
In-Reply-To: <alpine.DEB.2.21.1807171344320.12251@chino.kir.corp.google.com>
On 07/17/18 at 01:46pm, David Rientjes wrote:
> On Tue, 17 Jul 2018, Baoquan He wrote:
>
> > We can still use 'kernelcore=mirror' or 'movable_node' for the usage
> > of hotplug and movable zone. If somebody shows up with a valid usecase
> > we can reconsider.
> >
>
> We actively use kernelcore=n%, I had recently added support for the option
> in the first place in 4.17. It's certainly not deprecated.
Thanks for telling. Just for curiosity, could you tell the scenario you
are using kernelcore=n%? Since it evenly spread movable area on nodes,
we may not be able to physically hot unplug/plug RAM.
Thanks
Baoquan
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: mhocko@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, akpm@linux-foundation.org, corbet@lwn.net,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] mm/page_alloc: Deprecate kernelcore=nn and movable_core=
Date: Wed, 18 Jul 2018 07:31:00 +0800 [thread overview]
Message-ID: <20180717233100.GH1724@MiWiFi-R3L-srv> (raw)
In-Reply-To: <alpine.DEB.2.21.1807171344320.12251@chino.kir.corp.google.com>
On 07/17/18 at 01:46pm, David Rientjes wrote:
> On Tue, 17 Jul 2018, Baoquan He wrote:
>
> > We can still use 'kernelcore=mirror' or 'movable_node' for the usage
> > of hotplug and movable zone. If somebody shows up with a valid usecase
> > we can reconsider.
> >
>
> We actively use kernelcore=n%, I had recently added support for the option
> in the first place in 4.17. It's certainly not deprecated.
Thanks for telling. Just for curiosity, could you tell the scenario you
are using kernelcore=n%? Since it evenly spread movable area on nodes,
we may not be able to physically hot unplug/plug RAM.
Thanks
Baoquan
next prev parent reply other threads:[~2018-07-17 23:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 13:18 [PATCH] mm/page_alloc: Deprecate kernelcore=nn and movable_core= Baoquan He
2018-07-17 13:18 ` Baoquan He
2018-07-17 13:31 ` Michal Hocko
2018-07-17 13:31 ` Michal Hocko
2018-07-17 14:24 ` Baoquan He
2018-07-17 14:24 ` Baoquan He
2018-07-17 14:28 ` Michal Hocko
2018-07-17 14:28 ` Michal Hocko
2018-07-17 20:46 ` David Rientjes
2018-07-17 20:46 ` David Rientjes
2018-07-17 23:31 ` Baoquan He [this message]
2018-07-17 23:31 ` Baoquan He
2018-07-18 20:16 ` David Rientjes
2018-07-18 20:16 ` David Rientjes
2018-07-18 15:10 ` Michal Hocko
2018-07-18 15:10 ` Michal Hocko
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=20180717233100.GH1724@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rientjes@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.