Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-27 Thread Jungseok Lee
On May 27, 2015, at 1:10 PM, Minchan Kim wrote: > Hello Jungseok, Hi, Minchan, > On Tue, May 26, 2015 at 08:29:59PM +0900, Jungseok Lee wrote: >> On May 25, 2015, at 11:40 PM, Minchan Kim wrote: >>> Hello Jungseok, >> >> Hi, Minchan, >> >>> On Mon, May 25, 2015 at 01:02:20AM +0900, Jungseok

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-27 Thread Jungseok Lee
On May 27, 2015, at 4:31 PM, Arnd Bergmann wrote: > On Wednesday 27 May 2015 15:22:50 Sergey Senozhatsky wrote: >> On (05/27/15 13:10), Minchan Kim wrote: >>> On Tue, May 26, 2015 at 08:29:59PM +0900, Jungseok Lee wrote: if (test_thread_flag(TIF_MEMDIE) && !(gfp_mask & __GFP_NOFAIL))

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-27 Thread Jungseok Lee
On May 27, 2015, at 1:24 PM, Minchan Kim wrote: Hi, Minchan, > On Tue, May 26, 2015 at 09:10:11PM +0900, Jungseok Lee wrote: >> On May 25, 2015, at 11:58 PM, Minchan Kim wrote: >>> On Mon, May 25, 2015 at 07:01:33PM +0900, Jungseok Lee wrote: On May 25, 2015, at 2:49 AM, Arnd Bergmann

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-27 Thread Arnd Bergmann
On Wednesday 27 May 2015 15:22:50 Sergey Senozhatsky wrote: > On (05/27/15 13:10), Minchan Kim wrote: > > On Tue, May 26, 2015 at 08:29:59PM +0900, Jungseok Lee wrote: > > > > > > if (test_thread_flag(TIF_MEMDIE) && !(gfp_mask & __GFP_NOFAIL)) > > > goto nopage; > > > > > > IMHO, a reclaim

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-27 Thread Sergey Senozhatsky
On (05/27/15 13:10), Minchan Kim wrote: > On Tue, May 26, 2015 at 08:29:59PM +0900, Jungseok Lee wrote: > > On May 25, 2015, at 11:40 PM, Minchan Kim wrote: > > > Hello Jungseok, > > > > Hi, Minchan, > > > > > On Mon, May 25, 2015 at 01:02:20AM +0900, Jungseok Lee wrote: > > >> Fork-routine

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-27 Thread Jungseok Lee
On May 27, 2015, at 4:31 PM, Arnd Bergmann wrote: On Wednesday 27 May 2015 15:22:50 Sergey Senozhatsky wrote: On (05/27/15 13:10), Minchan Kim wrote: On Tue, May 26, 2015 at 08:29:59PM +0900, Jungseok Lee wrote: if (test_thread_flag(TIF_MEMDIE) !(gfp_mask __GFP_NOFAIL)) goto nopage;

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-27 Thread Jungseok Lee
On May 27, 2015, at 1:24 PM, Minchan Kim wrote: Hi, Minchan, On Tue, May 26, 2015 at 09:10:11PM +0900, Jungseok Lee wrote: On May 25, 2015, at 11:58 PM, Minchan Kim wrote: On Mon, May 25, 2015 at 07:01:33PM +0900, Jungseok Lee wrote: On May 25, 2015, at 2:49 AM, Arnd Bergmann wrote: On

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-27 Thread Jungseok Lee
On May 27, 2015, at 1:10 PM, Minchan Kim wrote: Hello Jungseok, Hi, Minchan, On Tue, May 26, 2015 at 08:29:59PM +0900, Jungseok Lee wrote: On May 25, 2015, at 11:40 PM, Minchan Kim wrote: Hello Jungseok, Hi, Minchan, On Mon, May 25, 2015 at 01:02:20AM +0900, Jungseok Lee wrote:

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-27 Thread Sergey Senozhatsky
On (05/27/15 13:10), Minchan Kim wrote: On Tue, May 26, 2015 at 08:29:59PM +0900, Jungseok Lee wrote: On May 25, 2015, at 11:40 PM, Minchan Kim wrote: Hello Jungseok, Hi, Minchan, On Mon, May 25, 2015 at 01:02:20AM +0900, Jungseok Lee wrote: Fork-routine sometimes fails to get

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-27 Thread Arnd Bergmann
On Wednesday 27 May 2015 15:22:50 Sergey Senozhatsky wrote: On (05/27/15 13:10), Minchan Kim wrote: On Tue, May 26, 2015 at 08:29:59PM +0900, Jungseok Lee wrote: if (test_thread_flag(TIF_MEMDIE) !(gfp_mask __GFP_NOFAIL)) goto nopage; IMHO, a reclaim operation would be not

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Minchan Kim
On Tue, May 26, 2015 at 09:10:11PM +0900, Jungseok Lee wrote: > On May 25, 2015, at 11:58 PM, Minchan Kim wrote: > > On Mon, May 25, 2015 at 07:01:33PM +0900, Jungseok Lee wrote: > >> On May 25, 2015, at 2:49 AM, Arnd Bergmann wrote: > >>> On Monday 25 May 2015 01:02:20 Jungseok Lee wrote: >

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Minchan Kim
Hello Jungseok, On Tue, May 26, 2015 at 08:29:59PM +0900, Jungseok Lee wrote: > On May 25, 2015, at 11:40 PM, Minchan Kim wrote: > > Hello Jungseok, > > Hi, Minchan, > > > On Mon, May 25, 2015 at 01:02:20AM +0900, Jungseok Lee wrote: > >> Fork-routine sometimes fails to get a physically

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Arnd Bergmann
On Tuesday 26 May 2015 01:36:29 Catalin Marinas wrote: > > > There are a lot of workloads that would benefit from having lower > > per-thread memory cost. > > If we keep the 16KB stack, is there any advantage in a separate IRQ one > (assuming > that we won't overflow 16KB)? It makes possible

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Jungseok Lee
On May 26, 2015, at 1:47 AM, Catalin Marinas wrote: > On 25 May 2015, at 13:01, Jungseok Lee wrote: > >>> Could the stack size be reduced to 8KB perhaps? >> >> I guess probably not. >> >> A commit, 845ad05e, says that 8KB is not enough to cover SpecWeb benchmark. > > We could go back to 8KB

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Jungseok Lee
On May 25, 2015, at 11:58 PM, Minchan Kim wrote: > On Mon, May 25, 2015 at 07:01:33PM +0900, Jungseok Lee wrote: >> On May 25, 2015, at 2:49 AM, Arnd Bergmann wrote: >>> On Monday 25 May 2015 01:02:20 Jungseok Lee wrote: Fork-routine sometimes fails to get a physically contiguous region for

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Jungseok Lee
On May 25, 2015, at 11:40 PM, Minchan Kim wrote: > Hello Jungseok, Hi, Minchan, > On Mon, May 25, 2015 at 01:02:20AM +0900, Jungseok Lee wrote: >> Fork-routine sometimes fails to get a physically contiguous region for >> thread_info on 4KB page system although free memory is enough. That is, >>

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Jungseok Lee
On May 26, 2015, at 11:52 AM, yalin wang wrote: > 2015-05-25 0:02 GMT+08:00 Jungseok Lee : >> Fork-routine sometimes fails to get a physically contiguous region for >> thread_info on 4KB page system although free memory is enough. That is, >> a physically contiguous region, which is currently

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Minchan Kim
Hello Jungseok, On Tue, May 26, 2015 at 08:29:59PM +0900, Jungseok Lee wrote: On May 25, 2015, at 11:40 PM, Minchan Kim wrote: Hello Jungseok, Hi, Minchan, On Mon, May 25, 2015 at 01:02:20AM +0900, Jungseok Lee wrote: Fork-routine sometimes fails to get a physically contiguous region

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Minchan Kim
On Tue, May 26, 2015 at 09:10:11PM +0900, Jungseok Lee wrote: On May 25, 2015, at 11:58 PM, Minchan Kim wrote: On Mon, May 25, 2015 at 07:01:33PM +0900, Jungseok Lee wrote: On May 25, 2015, at 2:49 AM, Arnd Bergmann wrote: On Monday 25 May 2015 01:02:20 Jungseok Lee wrote: Fork-routine

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Jungseok Lee
On May 25, 2015, at 11:40 PM, Minchan Kim wrote: Hello Jungseok, Hi, Minchan, On Mon, May 25, 2015 at 01:02:20AM +0900, Jungseok Lee wrote: Fork-routine sometimes fails to get a physically contiguous region for thread_info on 4KB page system although free memory is enough. That is, a

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Jungseok Lee
On May 25, 2015, at 11:58 PM, Minchan Kim wrote: On Mon, May 25, 2015 at 07:01:33PM +0900, Jungseok Lee wrote: On May 25, 2015, at 2:49 AM, Arnd Bergmann wrote: On Monday 25 May 2015 01:02:20 Jungseok Lee wrote: Fork-routine sometimes fails to get a physically contiguous region for

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Jungseok Lee
On May 26, 2015, at 11:52 AM, yalin wang wrote: 2015-05-25 0:02 GMT+08:00 Jungseok Lee jungseokle...@gmail.com: Fork-routine sometimes fails to get a physically contiguous region for thread_info on 4KB page system although free memory is enough. That is, a physically contiguous region, which

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Jungseok Lee
On May 26, 2015, at 1:47 AM, Catalin Marinas wrote: On 25 May 2015, at 13:01, Jungseok Lee jungseokle...@gmail.com wrote: Could the stack size be reduced to 8KB perhaps? I guess probably not. A commit, 845ad05e, says that 8KB is not enough to cover SpecWeb benchmark. We could go back

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-26 Thread Arnd Bergmann
On Tuesday 26 May 2015 01:36:29 Catalin Marinas wrote: There are a lot of workloads that would benefit from having lower per-thread memory cost. If we keep the 16KB stack, is there any advantage in a separate IRQ one (assuming that we won't overflow 16KB)? It makes possible errors

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread yalin wang
2015-05-25 0:02 GMT+08:00 Jungseok Lee : > Fork-routine sometimes fails to get a physically contiguous region for > thread_info on 4KB page system although free memory is enough. That is, > a physically contiguous region, which is currently 16KB, is not available > since system memory is

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Catalin Marinas
On 25 May 2015, at 23:29, Arnd Bergmann wrote: > On Monday 25 May 2015 19:47:15 Catalin Marinas wrote: >> On 25 May 2015, at 13:01, Jungseok Lee wrote: Could the stack size be reduced to 8KB perhaps? >>> >>> I guess probably not. >>> >>> A commit, 845ad05e, says that 8KB is not enough to

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Arnd Bergmann
On Monday 25 May 2015 19:01:33 Jungseok Lee wrote: > On May 25, 2015, at 2:49 AM, Arnd Bergmann wrote: > > Could the stack size be reduced to 8KB perhaps? > > I guess probably not. > > A commit, 845ad05e, says that 8KB is not enough to cover SpecWeb benchmark. > The stack size is 16KB on

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Arnd Bergmann
On Monday 25 May 2015 19:47:15 Catalin Marinas wrote: > On 25 May 2015, at 13:01, Jungseok Lee wrote: > > >> Could the stack size be reduced to 8KB perhaps? > > > > I guess probably not. > > > > A commit, 845ad05e, says that 8KB is not enough to cover SpecWeb benchmark. > > We could go back

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Catalin Marinas
On 25 May 2015, at 13:01, Jungseok Lee wrote: >> Could the stack size be reduced to 8KB perhaps? > > I guess probably not. > > A commit, 845ad05e, says that 8KB is not enough to cover SpecWeb benchmark. We could go back to 8KB stacks if we implement support for separate IRQ stack on arm64.

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Minchan Kim
On Mon, May 25, 2015 at 07:01:33PM +0900, Jungseok Lee wrote: > On May 25, 2015, at 2:49 AM, Arnd Bergmann wrote: > > On Monday 25 May 2015 01:02:20 Jungseok Lee wrote: > >> Fork-routine sometimes fails to get a physically contiguous region for > >> thread_info on 4KB page system although free

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Minchan Kim
Hello Jungseok, On Mon, May 25, 2015 at 01:02:20AM +0900, Jungseok Lee wrote: > Fork-routine sometimes fails to get a physically contiguous region for > thread_info on 4KB page system although free memory is enough. That is, > a physically contiguous region, which is currently 16KB, is not

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Jungseok Lee
On May 25, 2015, at 2:49 AM, Arnd Bergmann wrote: > On Monday 25 May 2015 01:02:20 Jungseok Lee wrote: >> Fork-routine sometimes fails to get a physically contiguous region for >> thread_info on 4KB page system although free memory is enough. That is, >> a physically contiguous region, which is

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Jungseok Lee
On May 25, 2015, at 2:49 AM, Arnd Bergmann wrote: On Monday 25 May 2015 01:02:20 Jungseok Lee wrote: Fork-routine sometimes fails to get a physically contiguous region for thread_info on 4KB page system although free memory is enough. That is, a physically contiguous region, which is currently

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Minchan Kim
Hello Jungseok, On Mon, May 25, 2015 at 01:02:20AM +0900, Jungseok Lee wrote: Fork-routine sometimes fails to get a physically contiguous region for thread_info on 4KB page system although free memory is enough. That is, a physically contiguous region, which is currently 16KB, is not available

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Catalin Marinas
On 25 May 2015, at 13:01, Jungseok Lee jungseokle...@gmail.com wrote: Could the stack size be reduced to 8KB perhaps? I guess probably not. A commit, 845ad05e, says that 8KB is not enough to cover SpecWeb benchmark. We could go back to 8KB stacks if we implement support for separate IRQ

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Minchan Kim
On Mon, May 25, 2015 at 07:01:33PM +0900, Jungseok Lee wrote: On May 25, 2015, at 2:49 AM, Arnd Bergmann wrote: On Monday 25 May 2015 01:02:20 Jungseok Lee wrote: Fork-routine sometimes fails to get a physically contiguous region for thread_info on 4KB page system although free memory is

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Arnd Bergmann
On Monday 25 May 2015 19:47:15 Catalin Marinas wrote: On 25 May 2015, at 13:01, Jungseok Lee jungseokle...@gmail.com wrote: Could the stack size be reduced to 8KB perhaps? I guess probably not. A commit, 845ad05e, says that 8KB is not enough to cover SpecWeb benchmark. We could

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Arnd Bergmann
On Monday 25 May 2015 19:01:33 Jungseok Lee wrote: On May 25, 2015, at 2:49 AM, Arnd Bergmann wrote: Could the stack size be reduced to 8KB perhaps? I guess probably not. A commit, 845ad05e, says that 8KB is not enough to cover SpecWeb benchmark. The stack size is 16KB on x86_64. I am

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread yalin wang
2015-05-25 0:02 GMT+08:00 Jungseok Lee jungseokle...@gmail.com: Fork-routine sometimes fails to get a physically contiguous region for thread_info on 4KB page system although free memory is enough. That is, a physically contiguous region, which is currently 16KB, is not available since system

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-25 Thread Catalin Marinas
On 25 May 2015, at 23:29, Arnd Bergmann a...@arndb.de wrote: On Monday 25 May 2015 19:47:15 Catalin Marinas wrote: On 25 May 2015, at 13:01, Jungseok Lee jungseokle...@gmail.com wrote: Could the stack size be reduced to 8KB perhaps? I guess probably not. A commit, 845ad05e, says that 8KB

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-24 Thread Arnd Bergmann
On Monday 25 May 2015 01:02:20 Jungseok Lee wrote: > Fork-routine sometimes fails to get a physically contiguous region for > thread_info on 4KB page system although free memory is enough. That is, > a physically contiguous region, which is currently 16KB, is not available > since system memory is

[RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-24 Thread Jungseok Lee
Fork-routine sometimes fails to get a physically contiguous region for thread_info on 4KB page system although free memory is enough. That is, a physically contiguous region, which is currently 16KB, is not available since system memory is fragmented. This patch tries to solve the problem as

Re: [RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-24 Thread Arnd Bergmann
On Monday 25 May 2015 01:02:20 Jungseok Lee wrote: Fork-routine sometimes fails to get a physically contiguous region for thread_info on 4KB page system although free memory is enough. That is, a physically contiguous region, which is currently 16KB, is not available since system memory is

[RFC PATCH 2/2] arm64: Implement vmalloc based thread_info allocator

2015-05-24 Thread Jungseok Lee
Fork-routine sometimes fails to get a physically contiguous region for thread_info on 4KB page system although free memory is enough. That is, a physically contiguous region, which is currently 16KB, is not available since system memory is fragmented. This patch tries to solve the problem as