Re: [PATCH] rust: add a ring buffer implementation

["Danilo Krummrich" <dakr@kernel.org>]

On Mon Feb 16, 2026 at 2:45 PM CET, Daniel Almeida wrote:
> With the allocation being handled by a separate component, I don’t think
> this is right. I think a better location is rust/kernel/io

I'm not sure it is reasonable to ask people who just want a ringbuffer in system
memory to take the indirection over an I/O ringbuffer implementation with
generic I/O backends choosing the system memory I/O backend.

The proposed code is simple, without comments and tests, less than 100 lines of
code. The I/O infrastructure to make this happen is still WIP. So, I think it's
fine to land it as VecDeque for now.

Once we have the I/O backend infrastructure, a system memory I/O backend that
can deal with separate allocators *and* a ring buffer implementation that sits
on top of it, we can still revisit if it makes sense to take advantage of
synergies.

But for now this seems a bit premature in terms of delaying Andreas' work.