Re: [f2fs-dev] write performance difference 3.18.21/4.2.1

2015-09-26 Thread Jaegeuk Kim
On Sat, Sep 26, 2015 at 05:22:18AM +0200, Marc Lehmann wrote: > On Fri, Sep 25, 2015 at 05:47:12PM +0800, Chao Yu > wrote: > > Please revert the commit 7c5e466755ff ("f2fs: readahead cp payload > > pages when mount") since in this commit we try to access invalid > >

Re: [f2fs-dev] write performance difference 3.18.21/4.2.1

2015-09-25 Thread Jaegeuk Kim
urceforge.net > > Subject: Re: [f2fs-dev] write performance difference 3.18.21/4.2.1 > > > > On Thu, Sep 24, 2015 at 11:28:36AM -0700, Jaegeuk Kim <jaeg...@kernel.org> > > wrote: > > > One thing that we can try is to run the latest f2fs source in v3.18.

Re: [f2fs-dev] write performance difference 3.18.21/4.2.1

2015-09-25 Thread Marc Lehmann
On Fri, Sep 25, 2015 at 05:47:12PM +0800, Chao Yu wrote: > Please revert the commit 7c5e466755ff ("f2fs: readahead cp payload > pages when mount") since in this commit we try to access invalid > SIT_I(sbi)->sit_base_addr which should be inited later. Wow, you are fast. To

Re: [f2fs-dev] write performance difference 3.18.21/4.2.1

2015-09-25 Thread Marc Lehmann
On Thu, Sep 24, 2015 at 11:28:36AM -0700, Jaegeuk Kim wrote: > One thing that we can try is to run the latest f2fs source in v3.18. > This branch supports f2fs for v3.18. Ok, please bear with me, the last time I built my own kernel was during the 2.4 timeframe, and this is a

Re: [f2fs-dev] write performance difference 3.18.21/4.2.1

2015-09-25 Thread Chao Yu
Hi Marc Jaegeuk, > -Original Message- > From: Marc Lehmann [mailto:schm...@schmorp.de] > Sent: Friday, September 25, 2015 2:51 PM > To: Jaegeuk Kim > Cc: linux-f2fs-devel@lists.sourceforge.net > Subject: Re: [f2fs-dev] write performance difference 3.18.21/4.2.1 > &

Re: [f2fs-dev] write performance difference 3.18.21/4.2.1

2015-09-24 Thread Jaegeuk Kim
On Thu, Sep 24, 2015 at 01:11:03AM +0200, Marc Lehmann wrote: > I tried twice with the same options, on linux 3.8.21 and 4.2.1, and write > performance is very different on these kernels (I rebooted every time in > between). > > On 3.18.21, the source raid is hardly able to keep up with the write

Re: [f2fs-dev] write performance difference 3.18.21/4.2.1

2015-09-24 Thread Marc Lehmann
On Thu, Sep 24, 2015 at 11:28:36AM -0700, Jaegeuk Kim wrote: > > The log starts after only 20GB had been written. Here is the status output > > at 25GB: > > > > http://ue.tst.eu/734f7883107ee4dabff77602db92310b.txt > > It seems about 700MB were moved by background GC. And

Re: [f2fs-dev] write performance difference 3.18.21/4.2.1

2015-09-24 Thread Marc Lehmann
On Fri, Sep 25, 2015 at 01:20:25AM +0200, Marc Lehmann wrote: > On Thu, Sep 24, 2015 at 11:28:36AM -0700, Jaegeuk Kim > wrote: > > > The log starts after only 20GB had been written. Here is the status output > > > at 25GB: > > > > > >

Re: [f2fs-dev] write performance difference 3.18.21/4.2.1

2015-09-23 Thread Marc Lehmann
I tried twice with the same options, on linux 3.8.21 and 4.2.1, and write performance is very different on these kernels (I rebooted every time in between). On 3.18.21, the source raid is hardly able to keep up with the write speed, f2fs basically writes at more or less full disk speed, for