Home
last modified time | relevance | path

Searched refs:avg_lat (Results 1 – 3 of 3) sorted by relevance

/linux/include/trace/events/
H A Df2fs.h2158 unsigned int avg_lat;
2203 __entry->d_rd_avg = iostat_lat[READ_IO][DATA].avg_lat;
2206 __entry->n_rd_avg = iostat_lat[READ_IO][NODE].avg_lat;
2209 __entry->m_rd_avg = iostat_lat[READ_IO][META].avg_lat;
2212 __entry->d_wr_s_avg = iostat_lat[WRITE_SYNC_IO][DATA].avg_lat;
2215 __entry->n_wr_s_avg = iostat_lat[WRITE_SYNC_IO][NODE].avg_lat;
2218 __entry->m_wr_s_avg = iostat_lat[WRITE_SYNC_IO][META].avg_lat;
2221 __entry->d_wr_as_avg = iostat_lat[WRITE_ASYNC_IO][DATA].avg_lat;
2224 __entry->n_wr_as_avg = iostat_lat[WRITE_ASYNC_IO][NODE].avg_lat;
2227 __entry->m_wr_as_avg = iostat_lat[WRITE_ASYNC_IO][META].avg_lat;
2159 unsigned int avg_lat; global() member
[all...]
/linux/fs/f2fs/
H A Diostat.c101 iostat_lat[idx][io].avg_lat = iostat_lat[idx][io].cnt ? in __record_iostat_latency()
/linux/Documentation/admin-guide/
H A Dcgroup-v2.rst2116 avg_lat value in io.stat for your workload group to get an idea of the
2117 latency you see during normal operation. Use the avg_lat value as a basis for
2161 avg_lat