From: Jens Axboe <[email protected]>
To: Nathan Ringo <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: sendto(), recvfrom()
Date: Fri, 26 Jun 2020 14:48:47 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <bRmxY0zzqGcGWE4Xg-O3jlU42WtEEMUb4iGvfOvesLybmoDNJ242_9phm-DHLM8zJzu7C63iKCZq4ZJLcrYXnuVewHvCgiO21tW2CSuabnE=@remexre.xyz>
On 6/26/20 2:47 PM, Nathan Ringo wrote:
> Would adding IORING_OP_{SENDTO,RECVFROM} be a reasonable first kernel
> contribution? I'd like to write a program with io_uring that's listening
> on a UDP socket, so recvfrom() at least is important to my use-case.
Certainly. When you hack it up, be sure to also provide a liburing
regression test case for test/ that tests the feature.
--
Jens Axboe
next prev parent reply other threads:[~2020-06-26 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 20:47 sendto(), recvfrom() Nathan Ringo
2020-06-26 20:48 ` Jens Axboe [this message]
2020-06-26 21:08 ` Jann Horn
2020-06-26 21:23 ` Nathan Ringo
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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