Home / server / Questions / 951226
Accepted
Craig Ringer
Asked: 2019-01-30 00:25:20 +0800 CST

What units are the I/O measures in GNU "time" in?

  • 772

GNU time has optional display of I/O measurements:

TIME="%I:%O" /usr/bin/time cp filea fileb
0:5488

but what units is it measuring? Any ideas? The manual only says

   %I     Number of filesystem inputs by the process.

   %O     Number of filesystem outputs by the process.

which is less than helpful.

A few tests suggest it is probably 512k blocks, both data and metadata:

$ TIME="%I:%O" /usr/bin/time dd if=/dev/zero of=foo bs=1 count=1024
1024 bytes (1.0 kB, 1.0 KiB) copied, 0.0120082 s, 85.3 kB/s
0:8

$ TIME="%I:%O" /usr/bin/time dd if=/dev/zero of=foo bs=1k count=1 conv=sync
1024 bytes (1.0 kB, 1.0 KiB) copied, 0.000354987 s, 2.9 MB/s
0:8

$ TIME="%I:%O" /usr/bin/time dd if=/dev/zero of=foo bs=1k count=1024
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.017763 s, 59.0 MB/s
0:2080

[craig@ayaki-localdomain personal-git]$ TIME="%I:%O" /usr/bin/time dd if=/dev/zero of=foo bs=1M count=1 conv=sync
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.0052077 s, 201 MB/s
0:2048

but it'd be nice to confirm that.

Anyone know where it comes from?

linux

2 Answers

  1. Best Answer

    From the manual:

    The `%I' and `%O' values are allegedly only `real'
input and output and do not include those supplied
by caching devices. The meaning of `real' I/O reported
by `%I' and `%O' may be muddled for workstations,
especially diskless ones.

    So units are in I/Os. Perhaps the source code knows what that means. From the summarize function documentation in time.c:

    ...
I == file system inputs (ru_inblock)
...
O == file system outputs (ru_oublock)
...

    ru_inblock and ru_oblock come from getrusage. From the getrusage manual:

    ru_inblock (since Linux 2.6.22)
  The number of times the filesystem had to perform input.

ru_oublock (since Linux 2.6.22)
  The number of times the filesystem had to perform output.

    Well that's not particularly useful, but LKML shows the patches being discussed(https://lkml.org/lkml/2007/3/19/100) to add ru_inblock and ru_oublock:

    As TASK_IO_ACCOUNTING currently counts bytes, we approximate blocks
count doing : nr_blocks = nr_bytes / 512

    A check on the current kernel source code(https://github.com/spotify/linux/blob/master/include/linux/task_io_accounting_ops.h) shows:

    /*
 * We approximate number of blocks, because we account bytes only.
 * A 'block' is 512 bytes
 */
static inline unsigned long task_io_get_inblock(const struct task_struct *p)
{
    return p->ioac.read_bytes >> 9;
}

    and

    /*
 * We approximate number of blocks, because we account bytes only.
 * A 'block' is 512 bytes
 */
static inline unsigned long task_io_get_oublock(const struct task_struct *p)
{
    return p->ioac.write_bytes >> 9;
}

    In short, yes, blocks are approximately 512 bytes each.

    • 4

  2. I would guess the "filesystem inputs/outputs" means the block size, so if the underlying filesystem has been formatted with 512 byte blocks, it returns that, if something else, then that.

    But this is just a guess.

    • 2