Re: [f2fs-dev] [PATCH v2] f2fs: move all the bio initialization into __bio_alloc

Hi, 2013-12-19 (목), 17:30 +0800, Gu Zheng: > Move all the bio initialization into __bio_alloc, and some minor cleanups are > also added. > > v2: > Use 'is_read' rather than 'rw' as Yu Chao suggested. > Remove the needless initialization of bio->bi_private. > > Signed-off-by: Gu Zheng > ---

Re: [f2fs-dev] [PATCH] f2fs: introduce a new direct_IO write path

Hi, 2013-12-20 (금), 10:14 +0800, Chao Yu: > Hi Kim, > > One comment as following: > > > -Original Message- > > From: Jaegeuk Kim [mailto:jaegeuk@samsung.com] > > Sent: Wednesday, December 18, 2013 8:12 AM > > To: linux-fsde...@vger.kernel.org > > Cc: linux-ker...@vger.kernel.org; lin

[f2fs-dev] [PATCH v3] f2fs: move all the bio initialization into __bio_alloc

Move all the bio initialization into __bio_alloc, and some minor cleanups are also added. v3: Use 'bool' rather than 'int' as Kim suggested. v2: Use 'is_read' rather than 'rw' as Yu Chao suggested. Remove the needless initialization of bio->bi_private. Signed-off-by: Gu Zheng --- fs/f2fs

[f2fs-dev] [PATCH] f2fs: remove the rw_flag domain from f2fs_io_info

When using the f2fs_io_info in the low level, we still need to merge the rw and rw_flag, so use the rw to hold all the io flags directly, and remove the rw_flag field. ps.It is based on the previous patch: f2fs: move all the bio initialization into __bio_alloc Signed-off-by: Gu Zheng --- fs/f2f

[f2fs-dev] [bug] writes hanging

Hello, I can't seem to write larger files on my f2fs mount. My hardware is an embedded arm platform with an 8GB eMMC nand flash chip: Golbalscale D2Plug I have two of these pieces of hardware and I see this issue on both of them. There