From: Daeho Jeong
Whenever we notice some sluggish issues on our machines, we are always
curious about how well all types of I/O in the f2fs filesystem are
handled. But, it's hard to get this kind of real data. First of all,
we need to reproduce the issue while turning on the profiling tool like
From: Daeho Jeong
Added F2FS_IOSTAT config option to support getting IO statistics through
sysfs and printing out periodic IO statistics tracepoint events and
moved I/O statistics related codes into separate files for better
maintenance.
Signed-off-by: Daeho Jeong
---
fs/f2fs/Kconfig
Ping this?
On Sun, Aug 8, 2021 at 2:52 PM Daeho Jeong wrote:
>
> From: Daeho Jeong
>
> Given fiemap way to print out extents in the kernel, we can correctly
> print the layout of each file in a unit of extent, not block. So, I
> changed fiemap print out way like below.
>
> Fiemap: offset = 0 len
On 2021/8/16 15:23, 李扬韬 wrote:
HI Chao,
SBI_NEED_FSCK is an indicator that fsck.f2fs needs to be triggered,
this flag is set in too many places. For some scenes that are not very
reproducible, adding stack information will help locate the problem.
Let's record all fsck stack history, I added F2
Don't create discard thread when device doesn't support realtime discard
or user specifies nodiscard mount option.
Signed-off-by: Fengnan Chang
Signed-off-by: Yangtao Li
Reviewed-by: Chao Yu
---
fs/f2fs/f2fs.h| 1 +
fs/f2fs/segment.c | 25 +++--
fs/f2fs/super.c | 27
1On 2021/8/16 15:22, Fengnan Chang wrote:
Don't create discard thread when device not support realtime discard.
Don't create discard thread when device doesn't support realtime discard
or user specifies nodiscard mount option.
Signed-off-by: Fengnan Chang
Signed-off-by: Yangtao Li
Otherw
