Re: [f2fs-dev] [PATCH v3] f2fs: reduce expensive checkpoint trigger frequency

>On 2024/6/25 10:14, wangzijie wrote: >>> We may trigger high frequent checkpoint for below case: >>> 1. mkdir /mnt/dir1; set dir1 encrypted >>> 2. touch /mnt/file1; fsync /mnt/file1 >>> 3. mkdir /mnt/dir2; set dir2 encrypted >>> 4. touch /mnt/file2; fsync /mnt/file2 >>> ... >>> >>> Although, newly

Re: [f2fs-dev] [PATCH v3] f2fs: reduce expensive checkpoint trigger frequency

On 2024/6/25 10:14, wangzijie wrote: We may trigger high frequent checkpoint for below case: 1. mkdir /mnt/dir1; set dir1 encrypted 2. touch /mnt/file1; fsync /mnt/file1 3. mkdir /mnt/dir2; set dir2 encrypted 4. touch /mnt/file2; fsync /mnt/file2 ... Although, newly created dir and file are not

Re: [f2fs-dev] [PATCH v3] f2fs: reduce expensive checkpoint trigger frequency

> We may trigger high frequent checkpoint for below case: > 1. mkdir /mnt/dir1; set dir1 encrypted > 2. touch /mnt/file1; fsync /mnt/file1 > 3. mkdir /mnt/dir2; set dir2 encrypted > 4. touch /mnt/file2; fsync /mnt/file2 > ... > > Although, newly created dir and file are not related, due to > commi

Re: [f2fs-dev] [PATCH v3] f2fs: reduce expensive checkpoint trigger frequency

Sorry, move jaegeuk to the "To" list Dear Jaegeuk, Let me describe the problem process, it is reproduced by monkey stability test: 1.SBI_NEED_CP flag bit is set， set_sbi_flag(F2FS_I_SB(inode), SBI_NEED_CP); 2.Ckpt thread is blocked by IO busy when it is doing CP, it can not get request t

Re: [f2fs-dev] [PATCH v3] f2fs: reduce expensive checkpoint trigger frequency

Dear Jaegeuk, Let me describe the problem process, it is reproduced by monkey stability test: 1.SBI_NEED_CP flag bit is set， set_sbi_flag(F2FS_I_SB(inode), SBI_NEED_CP); 2.Ckpt thread is blocked by IO busy when it is doing CP, it can not get request tag from block queue, PID: 505 TASK

Re: [f2fs-dev] [PATCH v3] f2fs: reduce expensive checkpoint trigger frequency

Jaegeuk, Any comments? On 2024/1/11 16:17, Chao Yu wrote: We may trigger high frequent checkpoint for below case: 1. mkdir /mnt/dir1; set dir1 encrypted 2. touch /mnt/file1; fsync /mnt/file1 3. mkdir /mnt/dir2; set dir2 encrypted 4. touch /mnt/file2; fsync /mnt/file2 ... Although, newly create

[f2fs-dev] [PATCH v3] f2fs: reduce expensive checkpoint trigger frequency

We may trigger high frequent checkpoint for below case: 1. mkdir /mnt/dir1; set dir1 encrypted 2. touch /mnt/file1; fsync /mnt/file1 3. mkdir /mnt/dir2; set dir2 encrypted 4. touch /mnt/file2; fsync /mnt/file2 ... Although, newly created dir and file are not related, due to commit bbf156f7afa7 ("f