linux.git/include/trace/events/f2fs.h, branch v6.8

f2fs: add tracepoint for f2fs_vm_page_mkwrite()

2023-12-11T21:37:53+00:00

This patch adds to support tracepoint for f2fs_vm_page_mkwrite(),
meanwhile it prints more details for trace_f2fs_filemap_fault().

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: show i_mode in trace_f2fs_new_inode()

2023-11-28T18:52:51+00:00

This patch supports to show i_mode field in trace_f2fs_new_inode().

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: introduce tracepoint for f2fs_rename()

2023-11-28T18:52:44+00:00

This patch adds tracepoints for f2fs_rename().

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: add async reset zone command support

2023-06-12T20:04:09+00:00

This patch enables submit reset zone command asynchornously. It helps
decrease average latency of write IOs in high utilization scenario by
faster checkpointing.

Signed-off-by: Daejun Park 
Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: Fix f2fs_truncate_partial_nodes ftrace event

2023-03-10T16:57:49+00:00

Fix the nid_t field so that its size is correctly reported in the text
format embedded in trace.dat files. As it stands, it is reported as
being of size 4:

        field:nid_t nid[3];     offset:24;      size:4; signed:0;

Instead of 12:

        field:nid_t nid[3];     offset:24;      size:12;        signed:0;

This also fixes the reported offset of subsequent fields so that they
match with the actual struct layout.

Signed-off-by: Douglas Raillard 
Reviewed-by: Mukesh Ojha 
Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: use iostat_lat_type directly as a parameter in the iostat_update_and_unbind_ctx()

2023-02-07T18:39:28+00:00

Convert to use iostat_lat_type as parameter instead of raw number.
BTW, move NUM_PREALLOC_IOSTAT_CTXS to the header file, adjust
iostat_lat[{0,1,2}] to iostat_lat[{READ_IO,WRITE_SYNC_IO,WRITE_ASYNC_IO}]
in tracepoint function, and rename iotype to page_type to match the definition.

Reported-by: kernel test robot 
Reported-by: Dan Carpenter 
Signed-off-by: Yangtao Li 
Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: introduce trace_f2fs_replace_atomic_write_block

2023-01-30T22:46:20+00:00

Commit 3db1de0e582c ("f2fs: change the current atomic write way")
removed old tracepoints, but it missed to add new one, this patch
fixes to introduce trace_f2fs_replace_atomic_write_block to trace
atomic_write commit flow.

Fixes: 3db1de0e582c ("f2fs: change the current atomic write way")
Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: support accounting iostat count and avg_bytes

2023-01-11T19:15:19+00:00

Previously, we supported to account iostat io_bytes,
in this patch, it adds to account iostat count and avg_bytes:

time:           1671648667
                        io_bytes         count            avg_bytes
[WRITE]
app buffered data:      31               2                15

Signed-off-by: Yangtao Li 
Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: remove the create argument to f2fs_map_blocks

2023-01-06T23:13:29+00:00

The create argument is always identicaly to map->m_may_create, so use
that consistently.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: add block_age-based extent cache

2022-12-12T22:53:56+00:00

This patch introduces a runtime hot/cold data separation method
for f2fs, in order to improve the accuracy for data temperature
classification, reduce the garbage collection overhead after
long-term data updates.

Enhanced hot/cold data separation can record data block update
frequency as "age" of the extent per inode, and take use of the age
info to indicate better temperature type for data block allocation:
 - It records total data blocks allocated since mount;
 - When file extent has been updated, it calculate the count of data
blocks allocated since last update as the age of the extent;
 - Before the data block allocated, it searches for the age info and
chooses the suitable segment for allocation.

Test and result:
 - Prepare: create about 30000 files
  * 3% for cold files (with cold file extension like .apk, from 3M to 10M)
  * 50% for warm files (with random file extension like .FcDxq, from 1K
to 4M)
  * 47% for hot files (with hot file extension like .db, from 1K to 256K)
 - create(5%)/random update(90%)/delete(5%) the files
  * total write amount is about 70G
  * fsync will be called for .db files, and buffered write will be used
for other files

The storage of test device is large enough(128G) so that it will not
switch to SSR mode during the test.

Benefit: dirty segment count increment reduce about 14%
 - before: Dirty +21110
 - after:  Dirty +18286

Signed-off-by: qixiaoyu1 
Signed-off-by: xiongping1 
Signed-off-by: Jaegeuk Kim