Re: [PATCH V5 16/17] mm: Let arch choose the initial value of task size

2017-03-29 Thread Anshuman Khandual
On 03/22/2017 09:07 AM, Aneesh Kumar K.V wrote: > As we start supporting larger address space (>128TB), we want to give > architecture a control on max task size of an application which is different > from the TASK_SIZE. For ex: ppc64 needs to track the base page size of a > segment > and it is co

Re: [PATCH V5 16/17] mm: Let arch choose the initial value of task size

2017-03-29 Thread Anshuman Khandual
On Wednesday 22 March 2017 09:07 AM, Aneesh Kumar K.V wrote: As we start supporting larger address space (>128TB), we want to give architecture a control on max task size of an application which is different from the TASK_SIZE. For ex: ppc64 needs to track the base page size of a segment and it

Re: [PATCH V5 16/17] mm: Let arch choose the initial value of task size

2017-03-28 Thread Aneesh Kumar K.V
On Tuesday 28 March 2017 04:47 PM, Michael Ellerman wrote: "Aneesh Kumar K.V" writes: As we start supporting larger address space (>128TB), we want to give architecture a control on max task size of an application which is different from the TASK_SIZE. For ex: ppc64 needs to track the base p

Re: [PATCH V5 16/17] mm: Let arch choose the initial value of task size

2017-03-28 Thread Michael Ellerman
"Aneesh Kumar K.V" writes: > As we start supporting larger address space (>128TB), we want to give > architecture a control on max task size of an application which is different > from the TASK_SIZE. For ex: ppc64 needs to track the base page size of a > segment > and it is copied from mm_contex

[PATCH V5 16/17] mm: Let arch choose the initial value of task size

2017-03-21 Thread Aneesh Kumar K.V
As we start supporting larger address space (>128TB), we want to give architecture a control on max task size of an application which is different from the TASK_SIZE. For ex: ppc64 needs to track the base page size of a segment and it is copied from mm_context_t to PACA on each context switch. If w