Home
last modified time | relevance | path

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

/linux-5.19.10/include/trace/events/
Df2fs.h1894 unsigned int avg_lat; member
1939 __entry->d_rd_avg = iostat_lat[0][DATA].avg_lat;
1942 __entry->n_rd_avg = iostat_lat[0][NODE].avg_lat;
1945 __entry->m_rd_avg = iostat_lat[0][META].avg_lat;
1948 __entry->d_wr_s_avg = iostat_lat[1][DATA].avg_lat;
1951 __entry->n_wr_s_avg = iostat_lat[1][NODE].avg_lat;
1954 __entry->m_wr_s_avg = iostat_lat[1][META].avg_lat;
1957 __entry->d_wr_as_avg = iostat_lat[2][DATA].avg_lat;
1960 __entry->n_wr_as_avg = iostat_lat[2][NODE].avg_lat;
1963 __entry->m_wr_as_avg = iostat_lat[2][META].avg_lat;
/linux-5.19.10/block/
Dblk-iolatency.c938 unsigned long long avg_lat; in iolatency_pd_stat() local
947 avg_lat = div64_u64(iolat->lat_avg, NSEC_PER_USEC); in iolatency_pd_stat()
951 avg_lat, cur_win); in iolatency_pd_stat()
954 iolat->rq_depth.max_depth, avg_lat, cur_win); in iolatency_pd_stat()
/linux-5.19.10/fs/f2fs/
Diostat.c103 iostat_lat[idx][io].avg_lat = cnt ? in __record_iostat_latency()
/linux-5.19.10/Documentation/admin-guide/
Dcgroup-v2.rst1897 avg_lat value in io.stat for your workload group to get an idea of the
1898 latency you see during normal operation. Use the avg_lat value as a basis for
1942 avg_lat