io_uring: Don't set the num_wait value during submit

The value is ignored if WAIT isn't indicated in the flags, but it's more
clear what is happening if left as zero as well.

Change-Id: Ib3539e37d1eaad6f5a68f6c028cdd186f12a8dd4
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2274994
Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Tested-by: Dylan Reid <dgreid@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
Commit-Queue: Dylan Reid <dgreid@chromium.org>
This commit is contained in:
Dylan Reid 2020-06-25 16:37:22 -07:00 committed by Commit Bot
parent 64a70c8003
commit e254389b63

View file

@ -455,7 +455,7 @@ impl URingContext {
self.stats.total_enter_calls = self.stats.total_enter_calls.wrapping_add(1);
unsafe {
// Safe because the only memory modified is in the completion queue.
io_uring_enter(self.ring_file.as_raw_fd(), self.added as u64, 1, 0)
io_uring_enter(self.ring_file.as_raw_fd(), self.added as u64, 0, 0)
.map_err(Error::RingEnter)?;
}
}