Re: [f2fs-dev] [PATCH v2] mkfs.f2fs: expand scalability of nat bitmap

On 2018/1/23 7:00, Jaegeuk Kim wrote: > On 01/17, Chao Yu wrote: >> Hi Jaegeuk, >> >> On 2018/1/17 8:47, Jaegeuk Kim wrote: >>> Hi Chao, >>> >>> On 01/15, Chao Yu wrote: Previously, our total node number (nat_bitmap) and total nat segment count will not monotonously increase along with

Re: [f2fs-dev] [PATCH v2] mkfs.f2fs: expand scalability of nat bitmap

On 01/17, Chao Yu wrote: > Hi Jaegeuk, > > On 2018/1/17 8:47, Jaegeuk Kim wrote: > > Hi Chao, > > > > On 01/15, Chao Yu wrote: > >> Previously, our total node number (nat_bitmap) and total nat segment count > >> will not monotonously increase along with image size, and max nat_bitmap > >> size

Re: [f2fs-dev] [PATCH v5] f2fs: add an ioctl to disable GC for specific file

This patch gives a flag to disable GC on given file, which would be useful, when user wants to keep its block map. It also conducts in-place-update for dontmove file. Reviewed-by: Chao Yu Signed-off-by: Jaegeuk Kim --- Change log from v1: - unset

[f2fs-dev] [PATCH v2] f2fs: support inode creation time

From: Chao Yu This patch adds creation time field in inode layout to support showing kstat.btime in ->statx. Signed-off-by: Chao Yu --- v2: - add missing sysfs entry. fs/f2fs/f2fs.h | 7 +++ fs/f2fs/file.c | 9 +

[f2fs-dev] [PATCH] fsck.f2fs: use mem nat info directly

Use mem nat info directly for we built in fsck init. Signed-off-by: Yunlei He --- fsck/mount.c | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/fsck/mount.c b/fsck/mount.c index 0a5b986..fe0d510 100644 --- a/fsck/mount.c +++ b/fsck/mount.c @@

[f2fs-dev] [PATCH 0/3] f2fs: support passing down write hints to block layer

From: Hyunchul Lee This set implements passing down write hints to block layer with the following mapping. This mapping equals the conclusion from discussion in the link, https://sourceforge.net/p/linux-f2fs/mailman/message/36170969/ But there are two exceptions. (1) the

[f2fs-dev] [PATCH 1/3] f2fs: support passing down write hints given by users to block layer

From: Hyunchul Lee Add the 'whint_mode' mount option that controls which write hints are passed down to block layer. There are "off" and "user-based" mode. The default mode is "off". 1) whint_mode=user-based. F2FS tries to pass down hints given by users. User

[f2fs-dev] [PATCH 2/3] f2fs: support passing down write hints to block layer with F2FS policy

From: Hyunchul Lee Add 'whint_mode=fs-based' mount option. In this mode, F2FS passes down write hints with its policy. * whint_mode=fs-based. F2FS passes down hints with its policy. User F2FS Block

[f2fs-dev] [PATCH 3/3] f2fs: Add the 'whint_mode' mount option to f2fs documentation

From: Hyunchul Lee Signed-off-by: Hyunchul Lee --- Documentation/filesystems/f2fs.txt | 6 ++ 1 file changed, 6 insertions(+) diff --git a/Documentation/filesystems/f2fs.txt b/Documentation/filesystems/f2fs.txt index 13c2ff0..414a160 100644 ---

[f2fs-dev] [PATCH] f2fs-tools: support inode creation time

This patch supports inode_crtime feature to enable recording inode creation time in inode layout. Signed-off-by: Chao Yu --- fsck/mount.c| 7 +++ include/f2fs_fs.h | 3 +++ mkfs/f2fs_format.c | 5 + mkfs/f2fs_format_main.c | 7 +++ 4 files

[f2fs-dev] [PATCH] f2fs: support inode creation time

This patch adds creation time field in inode layout to support showing kstat.btime in ->statx. Signed-off-by: Chao Yu --- fs/f2fs/f2fs.h | 7 +++ fs/f2fs/file.c | 9 + fs/f2fs/inode.c | 16 fs/f2fs/namei.c | 3

Re: [f2fs-dev] [PATCH RFC] f2fs: add PRE2 to mark segments free to one checkpoint but obsolete to the other

On 2018/1/22 16:03, guoweichao wrote: > > > On 2018/1/22 14:19, Chao Yu wrote: >> On 2018/1/22 10:40, guoweichao wrote: >>> Hi Chao, >>> >>> On 2018/1/21 10:34, Chao Yu wrote: Hi Weichao, On 2018/1/20 23:50, guoweichao wrote: > Hi Chao, > > Yes, it is exactly what I

Re: [f2fs-dev] [PATCH RFC] f2fs: add PRE2 to mark segments free to one checkpoint but obsolete to the other

On 2018/1/22 14:19, Chao Yu wrote: > On 2018/1/22 10:40, guoweichao wrote: >> Hi Chao, >> >> On 2018/1/21 10:34, Chao Yu wrote: >>> Hi Weichao, >>> >>> On 2018/1/20 23:50, guoweichao wrote: Hi Chao, Yes, it is exactly what I mean. It seems that F2FS has no responsibility to