Re: [PATCH 2/2] f2fs: remove alloc_nid_done/fail for performance

Sorry, please ignore this patch. 2013-05-08 (수), 09:56 +0900, Jaegeuk Kim: > This mechanism revealed two issues: bug and performance. > > Now, iput() doesn't guarantee that the inode is freed completely due to the > linked f2fs_drop_inode(). > So, in the case of failure on f2fs_new_inode(), we

[PATCH 2/2] f2fs: remove alloc_nid_done/fail for performance

This mechanism revealed two issues: bug and performance. Now, iput() doesn't guarantee that the inode is freed completely due to the linked f2fs_drop_inode(). So, in the case of failure on f2fs_new_inode(), we should not add the free nid again to the list even though iput() is called before then.

[PATCH 2/2] f2fs: remove alloc_nid_done/fail for performance

This mechanism revealed two issues: bug and performance. Now, iput() doesn't guarantee that the inode is freed completely due to the linked f2fs_drop_inode(). So, in the case of failure on f2fs_new_inode(), we should not add the free nid again to the list even though iput() is called before then.

Re: [PATCH 2/2] f2fs: remove alloc_nid_done/fail for performance

Sorry, please ignore this patch. 2013-05-08 (수), 09:56 +0900, Jaegeuk Kim: This mechanism revealed two issues: bug and performance. Now, iput() doesn't guarantee that the inode is freed completely due to the linked f2fs_drop_inode(). So, in the case of failure on f2fs_new_inode(), we should