On Sun 16-07-17 15:28:27, 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
Please describe _why_ the patch is needed. I suspect this is an
optimization but for which workloads it
On Sun 16-07-17 15:28:27, 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
Please describe _why_ the patch is needed. I suspect this is an
optimization but for which workloads it
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
Signed-off-by: Zhaoyang Huang
Signed-off-by: Zhaoyang Huang
---
mm/vmalloc.c | 7 +++
1 file
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
Signed-off-by: Zhaoyang Huang
Signed-off-by: Zhaoyang Huang
---
mm/vmalloc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/mm/vmalloc.c
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
Signed-off-by: Zhaoyang Huang
---
mm/vmalloc.c | 7 +++
1 file
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
Signed-off-by: Zhaoyang Huang
---
mm/vmalloc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
6 matches
Mail list logo