Al,
We saw a large regression (-55%) in a standard OLTP benchmark
between 3.15 kernel and 3.16-rc4 kernel.
One issue was caused by the changes in async direct IO in the
direct IO patch series between commit f6c0a192 and 62a8067a
for the 3.16-rc kernel. The kernel before this series at
commit 38583f09 has no such regression.
After some investigations and instrumentation, we saw that the
problem was caused by a lot of io_wait issued from
do_blockdev_direct_IO for async direct IO writes, which
did not happen for 3.15 kernel. The benchmark
used to run at 97% cpu utilization now has only
35% cpu utilization with plenty of idle time.
At the end of do_blockdev_direct_IO,
if (dio->is_async && retval == 0 && dio->result &&
((rw == READ) || (dio->result == sdio.size)))
retval = -EIOCBQUEUED;
if (retval != -EIOCBQUEUED)
dio_await_completion(dio);
we saw for async writes, the check
for (dio->result == sdio.size) failed. The retval was not
set to -EIOCBQUEUED, causing dio_await_completion to be issued
and hence the io_waits.
It is possible that the problem was introduced when dio->result
computation was moved into do_direct_IO in commit 3320c60b.
However, we cannot compile and test this commit separately as
it is dependent on some later patches in the direct IO patch series
so we have to test the patch series as a whole.
This is quite a large regression for us and we hope that
it can be fixed before 3.16 kernel is released.
Thanks.
Tim
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
