Re: [RFC PATCH] f2fs: obsolete FI_ACL_MODE

On 07/29, Chao Yu wrote: > Hi Jaegeuk, > > Could you take time to have a look at this? Is this change reasonable? > > Thanks, > > On 2017/7/26 22:33, Chao Yu wrote: > > From: Chao Yu > > > > Previously, in order to avoid losing important inode metadata after > > checkpoint

Re: [RFC PATCH] f2fs: obsolete FI_ACL_MODE

On 07/29, Chao Yu wrote: > Hi Jaegeuk, > > Could you take time to have a look at this? Is this change reasonable? > > Thanks, > > On 2017/7/26 22:33, Chao Yu wrote: > > From: Chao Yu > > > > Previously, in order to avoid losing important inode metadata after > > checkpoint & sudden power-off,

Re: [RFC PATCH] f2fs: obsolete FI_ACL_MODE

Hi Jaegeuk, Could you take time to have a look at this? Is this change reasonable? Thanks, On 2017/7/26 22:33, Chao Yu wrote: > From: Chao Yu > > Previously, in order to avoid losing important inode metadata after > checkpoint & sudden power-off, f2fs uses synchronous

Re: [RFC PATCH] f2fs: obsolete FI_ACL_MODE

Hi Jaegeuk, Could you take time to have a look at this? Is this change reasonable? Thanks, On 2017/7/26 22:33, Chao Yu wrote: > From: Chao Yu > > Previously, in order to avoid losing important inode metadata after > checkpoint & sudden power-off, f2fs uses synchronous approach for > updating

[RFC PATCH] f2fs: obsolete FI_ACL_MODE

From: Chao Yu Previously, in order to avoid losing important inode metadata after checkpoint & sudden power-off, f2fs uses synchronous approach for updating inode metadata, so attribute in inode cache will be updated to node page cache, after flushing dirty node pages in

[RFC PATCH] f2fs: obsolete FI_ACL_MODE

From: Chao Yu Previously, in order to avoid losing important inode metadata after checkpoint & sudden power-off, f2fs uses synchronous approach for updating inode metadata, so attribute in inode cache will be updated to node page cache, after flushing dirty node pages in checkpoint, these