Re: [PATCH 00/21] mm: introduce Designated Movable Blocks
From: Rob Herring <robh+dt@kernel.org>
Date: 2022-09-14 13:22:08
Also in:
linux-doc, linux-iommu, linux-mm, lkml
From: Rob Herring <robh+dt@kernel.org>
Date: 2022-09-14 13:22:08
Also in:
linux-doc, linux-iommu, linux-mm, lkml
On Tue, Sep 13, 2022 at 2:57 PM Doug Berger [off-list ref] wrote:
MOTIVATION: Some Broadcom devices (e.g. 7445, 7278) contain multiple memory controllers with each mapped in a different address range within a Uniform Memory Architecture. Some users of these systems have expressed the desire to locate ZONE_MOVABLE memory on each memory controller to allow user space intensive processing to make better use of the additional memory bandwidth. Unfortunately, the historical monotonic layout of zones would mean that if the lowest addressed memory controller contains ZONE_MOVABLE memory then all of the memory available from memory controllers at higher addresses must also be in the ZONE_MOVABLE zone. This would force all kernel memory accesses onto the lowest addressed memory controller and significantly reduce the amount of memory available for non-movable allocations.
Why are you sending kernel patches to the Devicetree specification list? Rob