crosvm/io_uring/Cargo.toml

[package]
name = "io_uring"
version = "0.1.0"
authors = ["The Chromium OS Authors"]
edition = "2018"

[dependencies]
data_model = { path = "../data_model" }
libc = "*"
syscall_defines = { path = "../syscall_defines" }
sync = { path = "../sync" }
sys_util = { path = "../sys_util" }

[dev-dependencies]
tempfile = { path = "../tempfile" }

[workspace]
Add io_uring interfaces Provide a low-level interface to operating the new io_uring interface. This is an unsafe interface with the basic operations of setting up the ring, adding to it, removing from it, and polling it. This will be followed by a safe interface layer on top of this code, then by additions to the asynchronous executor that allow for asynchronously doing multiple operations to files from one context. Change-Id: I71f7ffb04ce8cb4da470deda9aee768ab95d3d98 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2124009 Reviewed-by: Dylan Reid <dgreid@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Tested-by: Dylan Reid <dgreid@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Dylan Reid <dgreid@chromium.org> 2020-03-13 20:40:40 +00:00			`[package]`
			`name = "io_uring"`
			`version = "0.1.0"`
			`authors = ["The Chromium OS Authors"]`
			`edition = "2018"`

			`[dependencies]`
io_uring: Use IoBufMut instead of iovec This is ABI-compatible with iovec and comes with Send + Sync impls, which iovec does not have. BUG=none TEST=unit tests Change-Id: Ic5831f557933b1d0dc823b1f6ba991ffe57baf2c Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2571149 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org> Commit-Queue: Chirantan Ekbote <chirantan@chromium.org> 2020-12-03 09:18:20 +00:00			`data_model = { path = "../data_model" }`
Add io_uring interfaces Provide a low-level interface to operating the new io_uring interface. This is an unsafe interface with the basic operations of setting up the ring, adding to it, removing from it, and polling it. This will be followed by a safe interface layer on top of this code, then by additions to the asynchronous executor that allow for asynchronously doing multiple operations to files from one context. Change-Id: I71f7ffb04ce8cb4da470deda9aee768ab95d3d98 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2124009 Reviewed-by: Dylan Reid <dgreid@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Tested-by: Dylan Reid <dgreid@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Dylan Reid <dgreid@chromium.org> 2020-03-13 20:40:40 +00:00			`libc = "*"`
			`syscall_defines = { path = "../syscall_defines" }`
io_uring: Make UringContext Sync Rather than requiring callers to wrap the entire UringContext in a big lock, make UringContext Sync by internally using fine-grained locks: * The submit queue is wrapped with a Mutex so that threads may still add operations to the submit queue even when a thread is blocked inside an io_uring_enter call. * The completion queue internally uses a Mutex around the pending op data and completed count so that two threads don't end up trying to remove the same operation from the completed queue. With this we can enable the await_uring_from_poll test. This test uncovered missing wakeups in the case where a uring operation is added from one thread while the main uring thread is blocked inside an io_uring_enter syscall. To deal with this, we call submit() whenever the pending operation is polled and not yet submitted. BUG=none TEST=unit tests Change-Id: I4c7dec65c03b7b10014f4a84d2cd16fe8758ea72 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2643842 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Chirantan Ekbote <chirantan@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org> 2021-01-18 08:08:16 +00:00			`sync = { path = "../sync" }`
Refactor cros_async interface to avoid RawFd. Instead of creating IoSourceExt from AsRawFd implementers, we've switched to creating from a marker trait `IntoAsync`. This lets us use other types like RawDescriptor easily with this crate. By using the marker, we also provide some type safety by requiring consumers of IoSourceExt to declare that their type is expected to work with async operations. This way we can provide stronger guarantees that an async IO trait object will behave in a reasonable way. This CL also purges the cros_async -> base and io_uring -> base references, and provides the base types needed to add new async primitives to base. BUG=none TEST=builds Change-Id: I0b0ce6ca7938b22ae8e8fb4e604439f0292678f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2504481 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Noah Gold <nkgold@google.com> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org> 2020-11-06 03:10:36 +00:00			`sys_util = { path = "../sys_util" }`
Add io_uring interfaces Provide a low-level interface to operating the new io_uring interface. This is an unsafe interface with the basic operations of setting up the ring, adding to it, removing from it, and polling it. This will be followed by a safe interface layer on top of this code, then by additions to the asynchronous executor that allow for asynchronously doing multiple operations to files from one context. Change-Id: I71f7ffb04ce8cb4da470deda9aee768ab95d3d98 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2124009 Reviewed-by: Dylan Reid <dgreid@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Tested-by: Dylan Reid <dgreid@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Dylan Reid <dgreid@chromium.org> 2020-03-13 20:40:40 +00:00
			`[dev-dependencies]`
			`tempfile = { path = "../tempfile" }`

			`[workspace]`