From: Baoquan He <bhe@redhat.com>
To: Pingfan Liu <kernelfans@gmail.com>
Cc: Michal Hocko <mhocko@suse.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Mathieu Malaterre <malat@debian.org>,
kexec@lists.infradead.org, Daniel Vacek <neelx@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pavel Tatashin <pasha.tatashin@oracle.com>,
Nicholas Piggin <npiggin@gmail.com>,
Tang Chen <tangchen@cn.fujitsu.com>,
linux-acpi@vger.kernel.org,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
yinghai@kernel.org, Stefan Agner <stefan@agner.ch>,
Yaowei Bai <baiyaowei@cmss.chinamobile.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Young <dyoung@redhat.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
vgoyal@redhat.com, Len Brown <lenb@kernel.org>
Subject: Re: [PATCHv3 0/2] mm/memblock: reuse memblock bottom-up allocation style
Date: Fri, 28 Dec 2018 11:39:40 +0800 [thread overview]
Message-ID: <20181228033940.GB1990@MiWiFi-R3L-srv> (raw)
In-Reply-To: <1545966002-3075-1-git-send-email-kernelfans@gmail.com>
On 12/28/18 at 11:00am, Pingfan Liu wrote:
> The bottom-up allocation style is introduced to cope with movable_node,
> where the limit inferior of allocation starts from kernel's end, due to
> lack of knowledge of memory hotplug info at this early time.
> Beside this original aim, 'kexec -c' prefers to reuse this style to alloc mem
Wondering what is 'kexec -c'.
> at lower address, since if the reserved region is beyond 4G, then it requires
> extra mem (default is 16M) for swiotlb. But at this time hotplug info has been
The default is 256M, not sure if we are talking about the same thing.
low_size = max(swiotlb_size_or_default() + (8UL << 20), 256UL << 20);
> got, the limit inferior can be extend to 0, which is done by this series
>
> Cc: Tang Chen <tangchen@cn.fujitsu.com>
> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> Cc: Len Brown <lenb@kernel.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Mike Rapoport <rppt@linux.vnet.ibm.com>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Yaowei Bai <baiyaowei@cmss.chinamobile.com>
> Cc: Pavel Tatashin <pasha.tatashin@oracle.com>
> Cc: Nicholas Piggin <npiggin@gmail.com>
> Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
> Cc: Daniel Vacek <neelx@redhat.com>
> Cc: Mathieu Malaterre <malat@debian.org>
> Cc: Stefan Agner <stefan@agner.ch>
> Cc: Dave Young <dyoung@redhat.com>
> Cc: Baoquan He <bhe@redhat.com>
> Cc: yinghai@kernel.org,
> Cc: vgoyal@redhat.com
> Cc: linux-kernel@vger.kernel.org
>
> Pingfan Liu (2):
> mm/memblock: extend the limit inferior of bottom-up after parsing
> hotplug attr
> x86/kdump: bugfix, make the behavior of crashkernel=X consistent with
> kaslr
>
> arch/x86/kernel/setup.c | 9 +++++---
> drivers/acpi/numa.c | 4 ++++
> include/linux/memblock.h | 1 +
> mm/memblock.c | 58 +++++++++++++++++++++++++++++-------------------
> 4 files changed, 46 insertions(+), 26 deletions(-)
>
> --
> 2.7.4
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Pingfan Liu <kernelfans@gmail.com>
Cc: linux-acpi@vger.kernel.org, linux-mm@kvack.org,
kexec@lists.infradead.org, Tang Chen <tangchen@cn.fujitsu.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Michal Hocko <mhocko@suse.com>, Jonathan Corbet <corbet@lwn.net>,
Yaowei Bai <baiyaowei@cmss.chinamobile.com>,
Pavel Tatashin <pasha.tatashin@oracle.com>,
Nicholas Piggin <npiggin@gmail.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Daniel Vacek <neelx@redhat.com>,
Mathieu Malaterre <malat@debian.org>,
Stefan Agner <stefan@agner.ch>, Dave Young <dyoung@redhat.com>,
yinghai@kernel.org, vgoyal@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3 0/2] mm/memblock: reuse memblock bottom-up allocation style
Date: Fri, 28 Dec 2018 11:39:40 +0800 [thread overview]
Message-ID: <20181228033940.GB1990@MiWiFi-R3L-srv> (raw)
In-Reply-To: <1545966002-3075-1-git-send-email-kernelfans@gmail.com>
On 12/28/18 at 11:00am, Pingfan Liu wrote:
> The bottom-up allocation style is introduced to cope with movable_node,
> where the limit inferior of allocation starts from kernel's end, due to
> lack of knowledge of memory hotplug info at this early time.
> Beside this original aim, 'kexec -c' prefers to reuse this style to alloc mem
Wondering what is 'kexec -c'.
> at lower address, since if the reserved region is beyond 4G, then it requires
> extra mem (default is 16M) for swiotlb. But at this time hotplug info has been
The default is 256M, not sure if we are talking about the same thing.
low_size = max(swiotlb_size_or_default() + (8UL << 20), 256UL << 20);
> got, the limit inferior can be extend to 0, which is done by this series
>
> Cc: Tang Chen <tangchen@cn.fujitsu.com>
> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
> Cc: Len Brown <lenb@kernel.org>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Mike Rapoport <rppt@linux.vnet.ibm.com>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Yaowei Bai <baiyaowei@cmss.chinamobile.com>
> Cc: Pavel Tatashin <pasha.tatashin@oracle.com>
> Cc: Nicholas Piggin <npiggin@gmail.com>
> Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
> Cc: Daniel Vacek <neelx@redhat.com>
> Cc: Mathieu Malaterre <malat@debian.org>
> Cc: Stefan Agner <stefan@agner.ch>
> Cc: Dave Young <dyoung@redhat.com>
> Cc: Baoquan He <bhe@redhat.com>
> Cc: yinghai@kernel.org,
> Cc: vgoyal@redhat.com
> Cc: linux-kernel@vger.kernel.org
>
> Pingfan Liu (2):
> mm/memblock: extend the limit inferior of bottom-up after parsing
> hotplug attr
> x86/kdump: bugfix, make the behavior of crashkernel=X consistent with
> kaslr
>
> arch/x86/kernel/setup.c | 9 +++++---
> drivers/acpi/numa.c | 4 ++++
> include/linux/memblock.h | 1 +
> mm/memblock.c | 58 +++++++++++++++++++++++++++++-------------------
> 4 files changed, 46 insertions(+), 26 deletions(-)
>
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-12-28 3:40 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 3:00 [PATCHv3 0/2] mm/memblock: reuse memblock bottom-up allocation style Pingfan Liu
2018-12-28 3:00 ` Pingfan Liu
2018-12-28 3:00 ` [PATCHv3 1/2] mm/memblock: extend the limit inferior of bottom-up after parsing hotplug attr Pingfan Liu
2018-12-28 3:00 ` Pingfan Liu
2018-12-31 8:40 ` Mike Rapoport
2018-12-31 8:40 ` Mike Rapoport
2019-01-02 6:47 ` Pingfan Liu
2019-01-02 9:27 ` Mike Rapoport
2019-01-02 10:18 ` Baoquan He
2019-01-02 17:05 ` Mike Rapoport
2019-01-02 17:05 ` Mike Rapoport
2019-01-03 18:47 ` Tejun Heo
2019-01-03 18:47 ` Tejun Heo
2019-01-03 18:47 ` Tejun Heo
2019-01-04 15:09 ` Mike Rapoport
2019-01-04 15:09 ` Mike Rapoport
2019-01-04 15:09 ` Mike Rapoport
2019-01-05 3:44 ` Baoquan He
2019-01-05 3:44 ` Baoquan He
2019-01-06 6:27 ` Mike Rapoport
2019-01-06 6:27 ` Mike Rapoport
2019-01-08 8:50 ` Baoquan He
2019-01-08 8:50 ` Baoquan He
2019-01-07 8:37 ` Pingfan Liu
2019-01-07 8:37 ` Pingfan Liu
2019-01-04 5:59 ` Pingfan Liu
2019-01-04 5:59 ` Pingfan Liu
2019-01-04 16:20 ` Mike Rapoport
2019-01-04 16:20 ` Mike Rapoport
2018-12-28 3:00 ` [PATCHv3 2/2] x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr Pingfan Liu
2018-12-28 3:00 ` Pingfan Liu
2018-12-31 8:46 ` Mike Rapoport
2018-12-31 8:46 ` Mike Rapoport
2018-12-31 8:46 ` Mike Rapoport
2019-01-02 6:47 ` Pingfan Liu
2019-01-02 9:28 ` Mike Rapoport
2018-12-28 3:39 ` Baoquan He [this message]
2018-12-28 3:39 ` [PATCHv3 0/2] mm/memblock: reuse memblock bottom-up allocation style Baoquan He
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=20181228033940.GB1990@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=baiyaowei@cmss.chinamobile.com \
--cc=corbet@lwn.net \
--cc=dyoung@redhat.com \
--cc=kernelfans@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=malat@debian.org \
--cc=mhocko@suse.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=neelx@redhat.com \
--cc=npiggin@gmail.com \
--cc=pasha.tatashin@oracle.com \
--cc=rjw@rjwysocki.net \
--cc=rppt@linux.vnet.ibm.com \
--cc=stefan@agner.ch \
--cc=tangchen@cn.fujitsu.com \
--cc=vgoyal@redhat.com \
--cc=yinghai@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 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.