Re: [RFC PATCH 0/2] io_uring: add IPC channel infrastructure

[Jens Axboe]

On 3/16/26 6:49 AM, Daniel Hodges wrote:
> On Sat, Mar 14, 2026 at 10:54:15AM -0600, Jens Axboe wrote:
>> On 3/14/26 7:50 AM, Daniel Hodges wrote:
>>> On Thu, Mar 13, 2026 at 01:07:37PM +0000, Daniel Hodges wrote:
>>>> Performance (virtme-ng VM, single-socket, msg_size sweep 64B-32KB):
>>>>
>>>>   Point-to-point latency (64B-32KB messages):
>>>>     io_uring unicast: 597-3,185 ns/msg (within 1.5-2.5x of pipe for small msgs)
>>>
>>> Benchmark sources used to generate the numbers in the cover letter:
>>>
>>>   io_uring IPC modes (broadcast, multicast, unicast):
>>>     https://gist.github.com/hodgesds/fbcd8bb8497bc0ec2bf1f95244a984fe#file-io_uring_ipc_bench-c
>>>
>>>   IPC comparison (pipes, unix sockets, shm+eventfd):
>>>     https://gist.github.com/hodgesds/fbcd8bb8497bc0ec2bf1f95244a984fe#file-ipc_comparison_bench-c
>>
>> Thanks for sending these, was going to ask you about them. I'll take a
>> look at your patches Monday.
>>
>> -- 
>> Jens Axboe
> 
> No rush, thanks for taking the time!

I took a look - and I think it's quite apparent that it's a AI vibe
coded patch. Hence my first question is, do you have a specific use case
in mind? Or phrased differently, was this done for a specific use case
you have and want to pursue, or was it more of a "let's see if we can do
this and what it'd look like" kind of thing?

I have a lot of comments on the patch itself, but let's establish the
motivation here first.

-- 
Jens Axboe