Hello,
On Mon, May 09, 2016 at 10:26:08AM -0700, Jaegeuk Kim wrote:
> On Mon, May 09, 2016 at 03:35:25PM +, Stephen Bates wrote:
> > >
> > > We could figure out how to improve them. :)
> > >
> > > I've been preparing two patches under testing right now.
> > > - f2fs: fallocate data blocks i
On Fri, May 13, 2016 at 11:43:56AM +0800, Sheng Yong wrote:
> Hi, Kim
>
> On 5/13/2016 10:47 AM, Jaegeuk Kim wrote:
> > Hi Sheng,
> >
> > On Fri, May 13, 2016 at 10:22:40AM +0800, Sheng Yong wrote:
> >> This patch introduces a new struct f2fs_fault_info and a global f2fs_fault
> >> to save fault
Hi Yunlei,
It's just one atomic operation.
Are there performance or race condition issues?
Thanks,
On Fri, May 13, 2016 at 02:57:43PM +0800, Yunlei He wrote:
> No need inc dirty pages under inode lock
>
> Signed-off-by: Yunlei He
> ---
> fs/f2fs/checkpoint.c | 2 +-
> 1 file changed, 1 insert
Hello,
On Fri, May 13, 2016 at 11:47:29AM -0500, Jun He wrote:
> Hi,
>
> I understand that "F2FS does cleaning both on demand and in the
> background. On-demand cleaning is triggered when there are not enough
> free segments to serve VFS calls". Is there any way to start GC to
> clean all garbage
Hi,
I understand that "F2FS does cleaning both on demand and in the
background. On-demand cleaning is triggered when there are not enough
free segments to serve VFS calls". Is there any way to start GC to
clean all garbage even when the free segments are enough?
Thanks,
Jun
-