Christian Schwarz 168913bdf0 refactor(write path): newtype to enforce use of fully initialized slices (#8717) ...

The `tokio_epoll_uring::Slice` / `tokio_uring::Slice` type is weird.
The new `FullSlice` newtype is better. See the doc comment for details.

The naming is not ideal, but we'll clean that up in a future refactoring
where we move the `FullSlice` into `tokio_epoll_uring`. Then, we'll do
the following:
* tokio_epoll_uring::Slice is removed
* `FullSlice` becomes `tokio_epoll_uring::IoBufView`
* new type `tokio_epoll_uring::IoBufMutView` for the current
`tokio_epoll_uring::Slice<IoBufMut>`

Context
-------

I did this work in preparation for
https://github.com/neondatabase/neon/pull/8537.
There, I'm changing the type that the `inmemory_layer.rs` passes to
`DeltaLayerWriter::put_value_bytes` and thus it seemed like a good
opportunity to make this cleanup first.

2024-08-14 21:57:17 +02:00

..

io_engine

fixup(#7160 / tokio_epoll_uring_ext): double-panic caused by info! in thread-local's drop() (#7164)

2024-03-18 16:12:01 +01:00

owned_buffers_io

refactor(write path): newtype to enforce use of fully initialized slices (#8717)

2024-08-14 21:57:17 +02:00

io_engine.rs

refactor(write path): newtype to enforce use of fully initialized slices (#8717)

2024-08-14 21:57:17 +02:00

metadata.rs

tokio-epoll-uring: use it on the layer-creating code paths (#6378)

2024-03-05 09:03:54 +00:00

open_options.rs

tokio-epoll-uring: retry on launch failures due to locked memory (#7141)

2024-03-15 19:46:15 +00:00