public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Mark Papadakis <[email protected]>,
	io-uring <[email protected]>
Subject: Re: SQE OP - sendfile
Date: Wed, 29 Apr 2020 18:39:32 +0300	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 29/04/2020 18:21, Mark Papadakis wrote:
> Greetings,
> 
> Are there any plans for an SENDFILE SQE OP?
> Using a pipe and 2 two SPLICE ops(using the LINK flag) for moving data from one file FD to a socket FD(for example) works - but it’s somewhat inconvenient and maybe more expensive than it would otherwise be if there was a dedicated op for a sendfile() like facility.
> 

I didn't dig deeply, but it's done by internally creating a pipe and leaving it
with a task up until it exits. I hope such pipes use only 1 page or so, but I
don't like the idea of having one per each io-wq thread (even lazily as it's
done now).

If we really want to do that, would probably need something more elaborate.
Jens may shed some light.

-- 
Pavel Begunkov

      reply	other threads:[~2020-04-29 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29 15:21 SQE OP - sendfile Mark Papadakis
2020-04-29 15:39 ` Pavel Begunkov [this message]

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