Re: [PATCH v2 4/4] powerpc/mm/radix: Create separate mappings for hot-plugged memory

2020-07-08 Thread Michael Ellerman
"Aneesh Kumar K.V" writes: > On 7/8/20 10:14 AM, Michael Ellerman wrote: >> "Aneesh Kumar K.V" writes: >>> To enable memory unplug without splitting kernel page table >>> mapping, we force the max mapping size to the LMB size. LMB >>> size is the unit in which hypervisor will do memory

Re: [PATCH v2 4/4] powerpc/mm/radix: Create separate mappings for hot-plugged memory

2020-07-08 Thread Aneesh Kumar K.V
On 7/8/20 10:14 AM, Michael Ellerman wrote: "Aneesh Kumar K.V" writes: To enable memory unplug without splitting kernel page table mapping, we force the max mapping size to the LMB size. LMB size is the unit in which hypervisor will do memory add/remove operation. This implies on pseries

Re: [PATCH v2 4/4] powerpc/mm/radix: Create separate mappings for hot-plugged memory

2020-07-07 Thread Michael Ellerman
"Aneesh Kumar K.V" writes: > To enable memory unplug without splitting kernel page table > mapping, we force the max mapping size to the LMB size. LMB > size is the unit in which hypervisor will do memory add/remove > operation. > > This implies on pseries system, we now end up mapping Please

[PATCH v2 4/4] powerpc/mm/radix: Create separate mappings for hot-plugged memory

2020-06-25 Thread Aneesh Kumar K.V
To enable memory unplug without splitting kernel page table mapping, we force the max mapping size to the LMB size. LMB size is the unit in which hypervisor will do memory add/remove operation. This implies on pseries system, we now end up mapping memory with 2M page size instead of 1G. To