Searched hist:"80 c545055dc7c1f7f487176fe0aac17896a4b7af" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/fs/f2fs/ |
| H A D | checkpoint.c | diff 80c545055dc7c1f7f487176fe0aac17896a4b7af Thu Aug 20 10:51:56 CDT 2015 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: use __GFP_NOFAIL to avoid infinite loop
__GFP_NOFAIL can avoid retrying the whole path of kmem_cache_alloc and
bio_alloc.
And, it also fixes the use cases of GFP_ATOMIC correctly.
Suggested-by: Chao Yu <chao2.yu@samsung.com>
Reviewed-by: Chao Yu <chao2.yu@samsung.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | node.c | diff 80c545055dc7c1f7f487176fe0aac17896a4b7af Thu Aug 20 10:51:56 CDT 2015 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: use __GFP_NOFAIL to avoid infinite loop
__GFP_NOFAIL can avoid retrying the whole path of kmem_cache_alloc and
bio_alloc.
And, it also fixes the use cases of GFP_ATOMIC correctly.
Suggested-by: Chao Yu <chao2.yu@samsung.com>
Reviewed-by: Chao Yu <chao2.yu@samsung.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | segment.c | diff 80c545055dc7c1f7f487176fe0aac17896a4b7af Thu Aug 20 10:51:56 CDT 2015 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: use __GFP_NOFAIL to avoid infinite loop
__GFP_NOFAIL can avoid retrying the whole path of kmem_cache_alloc and
bio_alloc.
And, it also fixes the use cases of GFP_ATOMIC correctly.
Suggested-by: Chao Yu <chao2.yu@samsung.com>
Reviewed-by: Chao Yu <chao2.yu@samsung.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | f2fs.h | diff 80c545055dc7c1f7f487176fe0aac17896a4b7af Thu Aug 20 10:51:56 CDT 2015 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: use __GFP_NOFAIL to avoid infinite loop
__GFP_NOFAIL can avoid retrying the whole path of kmem_cache_alloc and
bio_alloc.
And, it also fixes the use cases of GFP_ATOMIC correctly.
Suggested-by: Chao Yu <chao2.yu@samsung.com>
Reviewed-by: Chao Yu <chao2.yu@samsung.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|