From: Jens Axboe <axboe@kernel.dk>
To: Daniel Hodges <git@danielhodges.dev>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] io_uring: add IPC channel infrastructure
Date: Sat, 14 Mar 2026 10:54:15 -0600 [thread overview]
Message-ID: <873d56d8-6c1c-447f-ae70-870417c6de5a@kernel.dk> (raw)
In-Reply-To: <20260314135053.3334-1-git@danielhodges.dev>
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
next prev parent reply other threads:[~2026-03-14 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 13:07 [RFC PATCH 0/2] io_uring: add IPC channel infrastructure Daniel Hodges
2026-03-13 13:07 ` [RFC PATCH 1/2] io_uring: add high-performance " Daniel Hodges
2026-03-13 13:07 ` [RFC PATCH 2/2] selftests/ipc: Add io_uring IPC selftest Daniel Hodges
2026-03-14 13:50 ` [RFC PATCH 0/2] io_uring: add IPC channel infrastructure Daniel Hodges
2026-03-14 16:54 ` Jens Axboe [this message]
2026-03-14 17:09 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873d56d8-6c1c-447f-ae70-870417c6de5a@kernel.dk \
--to=axboe@kernel.dk \
--cc=git@danielhodges.dev \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox