Re: [PATCH] mm: Support memblock alloc on the exact node for sparse_buffer_init()

2019-09-19 Thread Yunfeng Ye
On 2019/9/19 17:28, Mike Rapoport wrote: > On Thu, Sep 19, 2019 at 03:14:22PM +0800, Yunfeng Ye wrote: >> >> >> On 2019/9/19 12:47, Mike Rapoport wrote: >>> Hi, >>> >>> On Wed, Sep 18, 2019 at 12:22:29PM +0800, Yunfeng Ye wrote: Currently, when memblock_find_in_range_node() fail on the exac

Re: [PATCH] mm: Support memblock alloc on the exact node for sparse_buffer_init()

2019-09-19 Thread Yunfeng Ye
On 2019/9/19 8:30, Wei Yang wrote: > On Wed, Sep 18, 2019 at 03:08:41PM +0800, Yunfeng Ye wrote: >> >> >> On 2019/9/18 14:51, Wei Yang wrote: >>> On Wed, Sep 18, 2019 at 12:22:29PM +0800, Yunfeng Ye wrote: Currently, when memblock_find_in_range_node() fail on the exact node, it will us

Re: [PATCH] mm: Support memblock alloc on the exact node for sparse_buffer_init()

2019-09-19 Thread Mike Rapoport
On Thu, Sep 19, 2019 at 03:14:22PM +0800, Yunfeng Ye wrote: > > > On 2019/9/19 12:47, Mike Rapoport wrote: > > Hi, > > > > On Wed, Sep 18, 2019 at 12:22:29PM +0800, Yunfeng Ye wrote: > >> Currently, when memblock_find_in_range_node() fail on the exact node, it > >> will use %NUMA_NO_NODE to find

Re: [PATCH] mm: Support memblock alloc on the exact node for sparse_buffer_init()

2019-09-19 Thread Yunfeng Ye
On 2019/9/19 12:47, Mike Rapoport wrote: > Hi, > > On Wed, Sep 18, 2019 at 12:22:29PM +0800, Yunfeng Ye wrote: >> Currently, when memblock_find_in_range_node() fail on the exact node, it >> will use %NUMA_NO_NODE to find memblock from other nodes. At present, >> the work is good, but when the l

Re: [PATCH] mm: Support memblock alloc on the exact node for sparse_buffer_init()

2019-09-18 Thread Mike Rapoport
Hi, On Wed, Sep 18, 2019 at 12:22:29PM +0800, Yunfeng Ye wrote: > Currently, when memblock_find_in_range_node() fail on the exact node, it > will use %NUMA_NO_NODE to find memblock from other nodes. At present, > the work is good, but when the large memory is insufficient and the > small memory is

Re: [PATCH] mm: Support memblock alloc on the exact node for sparse_buffer_init()

2019-09-18 Thread Wei Yang
On Wed, Sep 18, 2019 at 03:08:41PM +0800, Yunfeng Ye wrote: > > >On 2019/9/18 14:51, Wei Yang wrote: >> On Wed, Sep 18, 2019 at 12:22:29PM +0800, Yunfeng Ye wrote: >>> Currently, when memblock_find_in_range_node() fail on the exact node, it >>> will use %NUMA_NO_NODE to find memblock from other nod

Re: [PATCH] mm: Support memblock alloc on the exact node for sparse_buffer_init()

2019-09-18 Thread Yunfeng Ye
On 2019/9/18 14:51, Wei Yang wrote: > On Wed, Sep 18, 2019 at 12:22:29PM +0800, Yunfeng Ye wrote: >> Currently, when memblock_find_in_range_node() fail on the exact node, it >> will use %NUMA_NO_NODE to find memblock from other nodes. At present, >> the work is good, but when the large memory is

Re: [PATCH] mm: Support memblock alloc on the exact node for sparse_buffer_init()

2019-09-17 Thread Wei Yang
On Wed, Sep 18, 2019 at 12:22:29PM +0800, Yunfeng Ye wrote: >Currently, when memblock_find_in_range_node() fail on the exact node, it >will use %NUMA_NO_NODE to find memblock from other nodes. At present, >the work is good, but when the large memory is insufficient and the >small memory is enough,