Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

2017-02-05 Thread Hoeun Ryu
On Sun, Feb 5, 2017 at 7:18 PM, Michal Hocko wrote: > On Sat 04-02-17 11:01:32, Hoeun Ryu wrote: >> On Sat, Feb 4, 2017 at 2:52 AM, Andy Lutomirski wrote: >> > On Fri, Feb 3, 2017 at 8:42 AM, Hoeun Ryu wrote: >> >> On Sat, Feb 4, 2017 at 12:39 AM, Michal Hocko wrote: >> >>> On Sat 04-02-17 00:3

Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

2017-02-05 Thread Michal Hocko
On Sat 04-02-17 11:01:32, Hoeun Ryu wrote: > On Sat, Feb 4, 2017 at 2:52 AM, Andy Lutomirski wrote: > > On Fri, Feb 3, 2017 at 8:42 AM, Hoeun Ryu wrote: > >> On Sat, Feb 4, 2017 at 12:39 AM, Michal Hocko wrote: > >>> On Sat 04-02-17 00:30:05, Hoeun Ryu wrote: > Using virtually mapped stack

Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

2017-02-03 Thread Hoeun Ryu
On Sat, Feb 4, 2017 at 2:52 AM, Andy Lutomirski wrote: > On Fri, Feb 3, 2017 at 8:42 AM, Hoeun Ryu wrote: >> On Sat, Feb 4, 2017 at 12:39 AM, Michal Hocko wrote: >>> On Sat 04-02-17 00:30:05, Hoeun Ryu wrote: Using virtually mapped stack, kernel stacks are allocated via vmalloc. In th

Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

2017-02-03 Thread Andy Lutomirski
On Fri, Feb 3, 2017 at 8:42 AM, Hoeun Ryu wrote: > On Sat, Feb 4, 2017 at 12:39 AM, Michal Hocko wrote: >> On Sat 04-02-17 00:30:05, Hoeun Ryu wrote: >>> Using virtually mapped stack, kernel stacks are allocated via vmalloc. >>> In the current implementation, two stacks per cpu can be cached whe

Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

2017-02-03 Thread Michal Hocko
On Sat 04-02-17 01:42:56, Hoeun Ryu wrote: > On Sat, Feb 4, 2017 at 12:39 AM, Michal Hocko wrote: > > On Sat 04-02-17 00:30:05, Hoeun Ryu wrote: > >> Using virtually mapped stack, kernel stacks are allocated via vmalloc. > >> In the current implementation, two stacks per cpu can be cached when >

Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

2017-02-03 Thread Hoeun Ryu
On Sat, Feb 4, 2017 at 12:39 AM, Michal Hocko wrote: > On Sat 04-02-17 00:30:05, Hoeun Ryu wrote: >> Using virtually mapped stack, kernel stacks are allocated via vmalloc. >> In the current implementation, two stacks per cpu can be cached when >> tasks are freed and the cached stacks are used aga

Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

2017-02-03 Thread kbuild test robot
Hi Hoeun, [auto build test ERROR on next-20170203] [also build test ERROR on v4.10-rc6] [cannot apply to linus/master linux/master v4.9-rc8 v4.9-rc7 v4.9-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/li

Re: [PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

2017-02-03 Thread Michal Hocko
On Sat 04-02-17 00:30:05, Hoeun Ryu wrote: > Using virtually mapped stack, kernel stacks are allocated via vmalloc. > In the current implementation, two stacks per cpu can be cached when > tasks are freed and the cached stacks are used again in task duplications. > but the array for the cached sta

[PATCH 1/3] fork: dynamically allocate cache array for vmapped stacks using cpuhp

2017-02-03 Thread Hoeun Ryu
Using virtually mapped stack, kernel stacks are allocated via vmalloc. In the current implementation, two stacks per cpu can be cached when tasks are freed and the cached stacks are used again in task duplications. but the array for the cached stacks is statically allocated by per-cpu api. In thi