Re: [PATCH 3/3] f2fs: enhnace alloc_nid and build_free_nids flows

2013-04-25 Thread Namjae Jeon
2013/4/25, Jaegeuk Kim : > In order to avoid build_free_nid lock contention, let's change the order of > function calls as follows. > > At first, check whether there is enough free nids. > - If available, just get a free nid with spin_lock without any overhead. > - Otherwise, conduct

[PATCH 3/3] f2fs: enhnace alloc_nid and build_free_nids flows

2013-04-25 Thread Jaegeuk Kim
In order to avoid build_free_nid lock contention, let's change the order of function calls as follows. At first, check whether there is enough free nids. - If available, just get a free nid with spin_lock without any overhead. - Otherwise, conduct build_free_nids. : scan nat pages, journal

[PATCH 3/3] f2fs: enhnace alloc_nid and build_free_nids flows

2013-04-25 Thread Jaegeuk Kim
In order to avoid build_free_nid lock contention, let's change the order of function calls as follows. At first, check whether there is enough free nids. - If available, just get a free nid with spin_lock without any overhead. - Otherwise, conduct build_free_nids. : scan nat pages, journal

Re: [PATCH 3/3] f2fs: enhnace alloc_nid and build_free_nids flows

2013-04-25 Thread Namjae Jeon
2013/4/25, Jaegeuk Kim jaegeuk@samsung.com: In order to avoid build_free_nid lock contention, let's change the order of function calls as follows. At first, check whether there is enough free nids. - If available, just get a free nid with spin_lock without any overhead. - Otherwise,