public inbox for [email protected]
 help / color / mirror / Atom feed
* Feature: zero-copy splice API/opcode
@ 2020-01-09 14:58 Mark Papadakis
  2020-01-12 21:21 ` Pavel Begunkov
  0 siblings, 1 reply; 2+ messages in thread
From: Mark Papadakis @ 2020-01-09 14:58 UTC (permalink / raw)
  To: io-uring

Greetings,

I ‘ve been trying to replicate the benefits provided by sendfile() using e.g O_DIRECT access, together with IOSQE_IO_LINK in SQE flags and MSG_ZEROCOPY, but it doesn’t appear to work. Other ideas didn’t work either.

I would really appreciate a sendfile like SQE opcode, but maybe some sort of generic DMA/zero-copy based opcode based on splice semantics could be implemented, so that e.g a vmsplice() like alternative could also work.


(That would be the last remaining bit of functionality missing from io_uring, now that Jens has implemented support for IOSQE_ASYNC, IORING_REGISTER_EVENTFD_ASYNC and for managing epoll FDs, for enabling support for io_uring on https://github.com/phaistos-networks/TANK ).

Thank you,
@markpapadakis


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

* Re: Feature: zero-copy splice API/opcode
  2020-01-09 14:58 Feature: zero-copy splice API/opcode Mark Papadakis
@ 2020-01-12 21:21 ` Pavel Begunkov
  0 siblings, 0 replies; 2+ messages in thread
From: Pavel Begunkov @ 2020-01-12 21:21 UTC (permalink / raw)
  To: Mark Papadakis, io-uring


[-- Attachment #1.1: Type: text/plain, Size: 1151 bytes --]

On 09/01/2020 17:58, Mark Papadakis wrote:
> Greetings,
> 
> I ‘ve been trying to replicate the benefits provided by sendfile() using e.g O_DIRECT access, together with IOSQE_IO_LINK in SQE flags and MSG_ZEROCOPY, but it doesn’t appear to work. Other ideas didn’t work either.
> 
> I would really appreciate a sendfile like SQE opcode, but maybe some sort of generic DMA/zero-copy based opcode based on splice semantics could be implemented, so that e.g a vmsplice() like alternative could also work.
> 
Sounds interesting, I'll look into this. First, I want to dig a bit into
kernel's zero-copy and get an idea how to cover all use cases with a single
opcode, and that's probably keeping in mind p2p.

The obvious nuisance from  perspective is that it needs 2 fds. Any other concerns?

> 
> (That would be the last remaining bit of functionality missing from io_uring, now that Jens has implemented support for IOSQE_ASYNC, IORING_REGISTER_EVENTFD_ASYNC and for managing epoll FDs, for enabling support for io_uring on https://github.com/phaistos-networks/TANK ).
> 
> Thank you,
> @markpapadakis
> 

-- 
Pavel Begunkov


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

end of thread, other threads:[~2020-01-12 21:21 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-01-09 14:58 Feature: zero-copy splice API/opcode Mark Papadakis
2020-01-12 21:21 ` Pavel Begunkov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox