On 26/02/2020 01:24, Jens Axboe wrote: > It very much can complete the req after io_read() returns, that's what > happens for any async disk request! By the time io_read() returns, the > request could be completed, or it could just be in-flight. This is > different from lots of the other opcodes, where the actual call returns > completion sync (either success, or EAGAIN). For some reason, I've got the idea that it do the same things as __vfs_read/write. At least I don't see the difference between io_read_prep()+io_read() and new_sync_read(). Thanks for the explanation, I should drop these futile attempts. -- Pavel Begunkov
