Re: [PATCH v2] mm/vmalloc: terminate searching since one node found

2017-07-18 Thread Zhaoyang Huang
On Mon, Jul 17, 2017 at 4:29 PM, Michal Hocko wrote: > On Mon 17-07-17 15:27:31, Zhaoyang Huang wrote: >> From: Zhaoyang Huang >> >> It is no need to find the very beginning of the area within >> alloc_vmap_area, which can be done by judging

Re: [PATCH v2] mm/vmalloc: terminate searching since one node found

2017-07-18 Thread Zhaoyang Huang
On Mon, Jul 17, 2017 at 4:29 PM, Michal Hocko wrote: > On Mon 17-07-17 15:27:31, Zhaoyang Huang wrote: >> From: Zhaoyang Huang >> >> It is no need to find the very beginning of the area within >> alloc_vmap_area, which can be done by judging each node during the process >> >> For current

Re: [PATCH v2] mm/vmalloc: terminate searching since one node found

2017-07-17 Thread zijun_hu
On 07/17/2017 04:45 PM, zijun_hu wrote: > On 07/17/2017 04:07 PM, Zhaoyang Huang wrote: >> It is no need to find the very beginning of the area within >> alloc_vmap_area, which can be done by judging each node during the process >> >> For current approach, the worst case is that the starting node

Re: [PATCH v2] mm/vmalloc: terminate searching since one node found

2017-07-17 Thread zijun_hu
On 07/17/2017 04:45 PM, zijun_hu wrote: > On 07/17/2017 04:07 PM, Zhaoyang Huang wrote: >> It is no need to find the very beginning of the area within >> alloc_vmap_area, which can be done by judging each node during the process >> >> For current approach, the worst case is that the starting node

Re: [PATCH v2] mm/vmalloc: terminate searching since one node found

2017-07-17 Thread zijun_hu
On 07/17/2017 04:07 PM, Zhaoyang Huang wrote: > It is no need to find the very beginning of the area within > alloc_vmap_area, which can be done by judging each node during the process > > For current approach, the worst case is that the starting node which be found > for searching the

Re: [PATCH v2] mm/vmalloc: terminate searching since one node found

2017-07-17 Thread zijun_hu
On 07/17/2017 04:07 PM, Zhaoyang Huang wrote: > It is no need to find the very beginning of the area within > alloc_vmap_area, which can be done by judging each node during the process > > For current approach, the worst case is that the starting node which be found > for searching the

Re: [PATCH v2] mm/vmalloc: terminate searching since one node found

2017-07-17 Thread Michal Hocko
On Mon 17-07-17 15:27:31, Zhaoyang Huang wrote: > From: Zhaoyang Huang > > It is no need to find the very beginning of the area within > alloc_vmap_area, which can be done by judging each node during the process > > For current approach, the worst case is that

Re: [PATCH v2] mm/vmalloc: terminate searching since one node found

2017-07-17 Thread Michal Hocko
On Mon 17-07-17 15:27:31, Zhaoyang Huang wrote: > From: Zhaoyang Huang > > It is no need to find the very beginning of the area within > alloc_vmap_area, which can be done by judging each node during the process > > For current approach, the worst case is that the starting node which be found >

[PATCH v2] mm/vmalloc: terminate searching since one node found

2017-07-17 Thread Zhaoyang Huang
From: Zhaoyang Huang It is no need to find the very beginning of the area within alloc_vmap_area, which can be done by judging each node during the process For current approach, the worst case is that the starting node which be found for searching the

[PATCH v2] mm/vmalloc: terminate searching since one node found

2017-07-17 Thread Zhaoyang Huang
From: Zhaoyang Huang It is no need to find the very beginning of the area within alloc_vmap_area, which can be done by judging each node during the process For current approach, the worst case is that the starting node which be found for searching the 'vmap_area_list' is close to the 'vstart',