Searched refs:dk_xfer (Results 1 – 6 of 6) sorted by relevance
310 points[i][point_pos] = (our_stats[newstat].dk_xfer[0] in set_values()311 +our_stats[newstat].dk_xfer[1] in set_values()312 +our_stats[newstat].dk_xfer[2] in set_values()313 +our_stats[newstat].dk_xfer[3] in set_values()314 -our_stats[oldstat].dk_xfer[0] in set_values()315 -our_stats[oldstat].dk_xfer[1] in set_values()316 -our_stats[oldstat].dk_xfer[2] in set_values()317 -our_stats[oldstat].dk_xfer[3]) in set_values()
73 stats.dk_xfer[0] disk transfers. Only the first seems to have74 stats.dk_xfer[1] any real useful (nonzero) value? If these are75 stats.dk_xfer[2] similiar to what vmstat reports, these can76 stats.dk_xfer[3] be for different disks.
221 tmp_if_stats.packets.in = tmp_if_stats.packets.out = (ullong)(dstats[i].dk_xfer / 2); in get_iface_stats_sysctldisk()
465 perf->qlen = drive.dk_xfer; in DevGetPerfData()
571 int dk_xfer[4]; member
297 int dk_xfer[4]; member