Re: linux-next: Tree for May 4 --> mm: free_area_init: allow defining max_zone_pfn in descending order does increase memory use

2020-05-05 Thread Christian Borntraeger
On 04.05.20 23:08, Stephen Rothwell wrote: > Hi Mike, > > On Mon, 4 May 2020 18:44:10 +0300 Mike Rapoport wrote: >> >> Ho Christian, >> >> On Mon, May 04, 2020 at 04:50:06PM +0200, Christian Borntraeger wrote: >>> Mike, >>> commit 51a2f644fd020d5f090044825c388444d11029d ("mm: free_area_init:

Re: linux-next: Tree for May 4 --> mm: free_area_init: allow defining max_zone_pfn in descending order does increase memory use

2020-05-04 Thread Stephen Rothwell
Hi Mike, On Mon, 4 May 2020 18:44:10 +0300 Mike Rapoport wrote: > > Ho Christian, > > On Mon, May 04, 2020 at 04:50:06PM +0200, Christian Borntraeger wrote: > > Mike, > > commit 51a2f644fd020d5f090044825c388444d11029d ("mm: free_area_init: allow > > defining max_zone_pfn in descending order")

Re: linux-next: Tree for May 4 --> mm: free_area_init: allow defining max_zone_pfn in descending order does increase memory use

2020-05-04 Thread Mike Rapoport
Ho Christian, On Mon, May 04, 2020 at 04:50:06PM +0200, Christian Borntraeger wrote: > Mike, > commit 51a2f644fd020d5f090044825c388444d11029d ("mm: free_area_init: allow > defining max_zone_pfn in descending order") > does increase the memory use on s390 (e.g. 700 MB vs.1.8 GB). > > Something

Re: linux-next: Tree for May 4 --> mm: free_area_init: allow defining max_zone_pfn in descending order does increase memory use

2020-05-04 Thread Christian Borntraeger
Mike, commit 51a2f644fd020d5f090044825c388444d11029d ("mm: free_area_init: allow defining max_zone_pfn in descending order") does increase the memory use on s390 (e.g. 700 MB vs.1.8 GB). Something is odd in this patch. Any idea?

linux-next: Tree for May 4

2020-05-04 Thread Stephen Rothwell
Hi all, Changes since 20200501: My fixes tree contains: bbefc924d0ff ("ubsan: disable UBSAN_ALIGNMENT under COMPILE_TEST") 7cb1d38f52b1 ("drm/msm: Fix undefined "rd_full" link error") The qcom tree still had its build failure for which I reverted a commit. The keys tree gained a conflict

linux-next: Tree for May 4

2018-05-03 Thread Stephen Rothwell
Hi all, Changes since 20180503: Non-merge commits (relative to Linus' tree): 3965 3776 files changed, 154371 insertions(+), 67944 deletions(-) I have created today's linux-next tree at

linux-next: Tree for May 4

2018-05-03 Thread Stephen Rothwell
Hi all, Changes since 20180503: Non-merge commits (relative to Linus' tree): 3965 3776 files changed, 154371 insertions(+), 67944 deletions(-) I have created today's linux-next tree at

linux-next: Tree for May 4

2017-05-03 Thread Stephen Rothwell
Hi all, Please do not add any v4.13 destined material in your linux-next included branches until after v4.12-rc1 has been released. Changes since 20170503: The f2fs tree gained a conflict against the fscrypt tree. The spi-nor tree gained a build failure so I used the version from

linux-next: Tree for May 4

2017-05-03 Thread Stephen Rothwell
Hi all, Please do not add any v4.13 destined material in your linux-next included branches until after v4.12-rc1 has been released. Changes since 20170503: The f2fs tree gained a conflict against the fscrypt tree. The spi-nor tree gained a build failure so I used the version from

linux-next: Tree for May 4

2016-05-04 Thread Stephen Rothwell
Hi all, Changes since 20160503: Dropped tree: hsi (at the maintainer's request) The tip tree gained a conflict against the arc tree. The kvm-arm tree gained a conflict against the tip tree. Non-merge commits (relative to Linus' tree): 7982 6997 files changed, 298694 insertions(+), 148713

linux-next: Tree for May 4

2016-05-04 Thread Stephen Rothwell
Hi all, Changes since 20160503: Dropped tree: hsi (at the maintainer's request) The tip tree gained a conflict against the arc tree. The kvm-arm tree gained a conflict against the tip tree. Non-merge commits (relative to Linus' tree): 7982 6997 files changed, 298694 insertions(+), 148713

linux-next: Tree for May 4

2015-05-03 Thread Stephen Rothwell
Hi all, Changes since 20150501: Removed tree: virtio (maintainer moved on) The akpm-current tree lost its build failure. Non-merge commits (relative to Linus' tree): 1436 1426 files changed, 81272 insertions(+), 32795 deletions(-)

linux-next: Tree for May 4

2015-05-03 Thread Stephen Rothwell
Hi all, Changes since 20150501: Removed tree: virtio (maintainer moved on) The akpm-current tree lost its build failure. Non-merge commits (relative to Linus' tree): 1436 1426 files changed, 81272 insertions(+), 32795 deletions(-)