From: David Howells <dhowells@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: dhowells@redhat.com, io-uring@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: io_uring and crypto
Date: Tue, 07 Oct 2025 18:11:22 +0100 [thread overview]
Message-ID: <4016104.1759857082@warthog.procyon.org.uk> (raw)
Hi Jens,
I was wondering if it might be possible to adapt io_uring to make crypto
requests as io_uring primitives rather than just having io_uring call sendmsg
and recvmsg on an AF_ALG socket.
The reason I think this might make sense is that for the certain crypto ops we
need to pass two buffers, one input and one output (encrypt, decrypt, sign) or
two input (verify) and this could directly translate to an async crypto
request.
Or possibly we should have a sendrecv socket call (RPC sort of thing) and have
io_uring drive that.
The tricky bit is that it would require two buffers and io_uring seems geared
around one.
David
next reply other threads:[~2025-10-07 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 17:11 David Howells [this message]
2025-10-07 17:13 ` io_uring and crypto Eric Biggers
2025-10-07 17:27 ` 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=4016104.1759857082@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-crypto@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