Re: [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag

2014-09-14 Thread Minchan Kim
On Mon, Sep 15, 2014 at 10:10:18AM +0900, Joonsoo Kim wrote: > On Fri, Sep 05, 2014 at 10:14:16AM -0400, Theodore Ts'o wrote: > > On Fri, Sep 05, 2014 at 04:32:48PM +0900, Joonsoo Kim wrote: > > > I also test another approach, such as allocate freepage in CMA > > > reserved region as late as possib

Re: [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag

2014-09-14 Thread Joonsoo Kim
On Fri, Sep 05, 2014 at 10:14:16AM -0400, Theodore Ts'o wrote: > On Fri, Sep 05, 2014 at 04:32:48PM +0900, Joonsoo Kim wrote: > > I also test another approach, such as allocate freepage in CMA > > reserved region as late as possible, which is also similar to your > > suggestion and this doesn't wor

Re: [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag

2014-09-05 Thread Theodore Ts'o
On Fri, Sep 05, 2014 at 04:32:48PM +0900, Joonsoo Kim wrote: > I also test another approach, such as allocate freepage in CMA > reserved region as late as possible, which is also similar to your > suggestion and this doesn't works well. When reclaim is started, > too many pages reclaim at once, bec

Re: [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag

2014-09-05 Thread Joonsoo Kim
On Thu, Sep 04, 2014 at 11:17:35PM -0400, Theodore Ts'o wrote: > Joonson, > > Thanks for the update. I've applied Gioh's patches to the ext4 tree, > but I'd appreciate a further clarification. My understanding with the > problem you were trying to address is that with the current CMA > implement

Re: [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag

2014-09-04 Thread Theodore Ts'o
Joonson, Thanks for the update. I've applied Gioh's patches to the ext4 tree, but I'd appreciate a further clarification. My understanding with the problem you were trying to address is that with the current CMA implementation, kswapd was getting activiated too early, yes? But it would still be

Re: [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag

2014-09-04 Thread Joonsoo Kim
On Thu, Sep 04, 2014 at 09:14:19PM -0400, Theodore Ts'o wrote: > On Fri, Sep 05, 2014 at 09:37:05AM +0900, Gioh Kim wrote: > > >But what were the problems which were observed in standard kernels and > > >what effect did this patchset have upon them? Some quantitative > > >measurements will really

Re: [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag

2014-09-04 Thread Theodore Ts'o
On Fri, Sep 05, 2014 at 09:37:05AM +0900, Gioh Kim wrote: > >But what were the problems which were observed in standard kernels and > >what effect did this patchset have upon them? Some quantitative > >measurements will really help here. > > The problem is that I cannot allocate entire CMA memory

Re: [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag

2014-09-04 Thread Gioh Kim
2014-09-05 오전 7:16, Andrew Morton 쓴 글: On Thu, 4 Sep 2014 16:29:38 +0900 Gioh Kim wrote: This patch try to solve problem that a long-lasting page caches of ext4 superblock and journaling of superblock disturb page migration. I've been testing CMA feature on my ARM-based platform and found

Re: [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag

2014-09-04 Thread Andrew Morton
On Thu, 4 Sep 2014 16:29:38 +0900 Gioh Kim wrote: > This patch try to solve problem that a long-lasting page caches of > ext4 superblock and journaling of superblock disturb page migration. > > I've been testing CMA feature on my ARM-based platform > and found that two page caches cannot be mig

[PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag

2014-09-04 Thread Gioh Kim
Hello, This patch try to solve problem that a long-lasting page caches of ext4 superblock and journaling of superblock disturb page migration. I've been testing CMA feature on my ARM-based platform and found that two page caches cannot be migrated. They are page caches of superblock of ext4 files