Re: [PATCH 3/9] f2fs: remove redundant lock_page calls

2013-04-02 Thread Namjae Jeon
2013/4/1, Jaegeuk Kim : > In get_node_page, we do not need to call lock_page all the time. > > If the node page is cached as uptodate, > > 1. grab_cache_page locks the page, > 2. read_node_page unlocks the page, and > 3. lock_page is called for further process. > > Let's avoid this. Instead of

Re: [PATCH 3/9] f2fs: remove redundant lock_page calls

2013-04-02 Thread Namjae Jeon
2013/4/1, Jaegeuk Kim jaegeuk@samsung.com: In get_node_page, we do not need to call lock_page all the time. If the node page is cached as uptodate, 1. grab_cache_page locks the page, 2. read_node_page unlocks the page, and 3. lock_page is called for further process. Let's avoid this.

[PATCH 3/9] f2fs: remove redundant lock_page calls

2013-04-01 Thread Jaegeuk Kim
In get_node_page, we do not need to call lock_page all the time. If the node page is cached as uptodate, 1. grab_cache_page locks the page, 2. read_node_page unlocks the page, and 3. lock_page is called for further process. Let's avoid this. Signed-off-by: Jaegeuk Kim --- fs/f2fs/node.c | 63

[PATCH 3/9] f2fs: remove redundant lock_page calls

2013-04-01 Thread Jaegeuk Kim
In get_node_page, we do not need to call lock_page all the time. If the node page is cached as uptodate, 1. grab_cache_page locks the page, 2. read_node_page unlocks the page, and 3. lock_page is called for further process. Let's avoid this. Signed-off-by: Jaegeuk Kim jaegeuk@samsung.com