projects / blktrace.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b18f4c1) | patch
Use maximum over all traces for queue depth
authorJan Kara <jack@suse.com>
Thu, 5 May 2016 15:17:05 +0000 (17:17 +0200)
committerJens Axboe <axboe@fb.com>
Thu, 5 May 2016 15:20:18 +0000 (09:20 -0600)
commit5122a87b22ade9cf2920dc6f9e24ce1a745f3ff6
tree6879e556dd39e23ae542978c63ce0a967e4f38fatree | snapshot
parentb18f4c129dde9783be64d699e2f261bb6729f732commit | diff
Use maximum over all traces for queue depth

So far we used maximum of the first trace for the maximum range of the
queue depth graph. Use maximum over all traces similarly as for other
line graphs.

Signed-off-by: Jan Kara <jack@suse.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
iowatcher/main.c diff | blob | blame | history
Block queue io tracer