IO-Uring Archive on lore.kernel.org
 help / color / Atom feed
* sendto(), recvfrom()
@ 2020-06-26 20:47 Nathan Ringo
  2020-06-26 20:48 ` Jens Axboe
  2020-06-26 21:08 ` Jann Horn
  0 siblings, 2 replies; 4+ messages in thread
From: Nathan Ringo @ 2020-06-26 20:47 UTC (permalink / raw)
  To: io-uring

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.

--
Nathan Ringo


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: sendto(), recvfrom()
  2020-06-26 20:47 sendto(), recvfrom() Nathan Ringo
@ 2020-06-26 20:48 ` Jens Axboe
  2020-06-26 21:08 ` Jann Horn
  1 sibling, 0 replies; 4+ messages in thread
From: Jens Axboe @ 2020-06-26 20:48 UTC (permalink / raw)
  To: Nathan Ringo, io-uring

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: sendto(), recvfrom()
  2020-06-26 20:47 sendto(), recvfrom() Nathan Ringo
  2020-06-26 20:48 ` Jens Axboe
@ 2020-06-26 21:08 ` Jann Horn
  2020-06-26 21:23   ` Nathan Ringo
  1 sibling, 1 reply; 4+ messages in thread
From: Jann Horn @ 2020-06-26 21:08 UTC (permalink / raw)
  To: Nathan Ringo; +Cc: io-uring

On Fri, Jun 26, 2020 at 10:47 PM Nathan Ringo <nathan@remexre.xyz> 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.

What is the benefit compared to IORING_OP_RECVMSG and
IORING_OP_SENDMSG, which already exist (and provide a superset of
sendto/recvfrom)?

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: sendto(), recvfrom()
  2020-06-26 21:08 ` Jann Horn
@ 2020-06-26 21:23   ` Nathan Ringo
  0 siblings, 0 replies; 4+ messages in thread
From: Nathan Ringo @ 2020-06-26 21:23 UTC (permalink / raw)
  To: Jann Horn; +Cc: io-uring

On Friday, June 26, 2020 4:08 PM, Jann Horn <jannh@google.com> wrote:
> What is the benefit compared to IORING_OP_RECVMSG and
> IORING_OP_SENDMSG, which already exist (and provide a superset of
> sendto/recvfrom)?

Ah, I didn't realize this was the case, whoops. I guess I'm showing off
my lack of familiarity with Unix; I remembered sendmsg as being specific
to Unix domain sockets. I'll just use that, then.

--
Nathan Ringo

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-26 20:47 sendto(), recvfrom() Nathan Ringo
2020-06-26 20:48 ` Jens Axboe
2020-06-26 21:08 ` Jann Horn
2020-06-26 21:23   ` Nathan Ringo

IO-Uring Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/io-uring/0 io-uring/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 io-uring io-uring/ https://lore.kernel.org/io-uring \
		io-uring@vger.kernel.org
	public-inbox-index io-uring

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.io-uring


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git