public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Keith Busch <[email protected]>,
	[email protected],
	Alexander Viro <[email protected]>
Cc: [email protected], [email protected], [email protected],
	[email protected], Pavel Begunkov <[email protected]>,
	Eric Dumazet <[email protected]>,
	Steven Rostedt <[email protected]>,
	[email protected], Jakub Kicinski <[email protected]>,
	Paolo Abeni <[email protected]>,
	David Howells <[email protected]>,
	Jarkko Sakkinen <[email protected]>,
	Paul Moore <[email protected]>,
	[email protected], [email protected],
	[email protected], [email protected],
	[email protected], Keith Busch <[email protected]>
Subject: Re: [PATCHv2 00/12] iov_iter: replace import_single_range with ubuf
Date: Sun, 8 Jan 2023 20:51:43 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 1/5/23 12:07 PM, Keith Busch wrote:
> From: Keith Busch <[email protected]>
> 
> ITER_UBUF is a more efficient representation when using single vector
> buffers, providing small optimizations over ITER_IOVEC. This series
> introduces a helper to set these up, and replaces all applicable users
> of import_single_range with the new helper. And since there are no
> single range users left after this change, the helper is no longer
> needed.
> 
> As noted in v1(*), there are some fundamental differences to how io_uring
> compares to read/write/readv/writev. There are only the two affected
> file_operations, and they already do not work with io_uring due to their
> diverging semantics for vectored vs non-vectored read/write. Therefore,
> this series having io_uring prefer ubuf iov_iter isn't introducing new
> breakage.

Pondering how to stage this, both for later upstream but also for
testing. Would probably make the best sense to stage 1-5 separately,
and then just punt the remaining ones to the appropriate subsystems.
And then 12/12 can go in when they have all been applied.

-- 
Jens Axboe



  parent reply	other threads:[~2023-01-09  3:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <[email protected]>
2023-01-08 17:12 ` [PATCHv2 00/12] iov_iter: replace import_single_range with ubuf Christoph Hellwig
     [not found] ` <[email protected]>
2023-01-09  3:49   ` [PATCHv2 02/12] io_uring: switch network send/recv to ITER_UBUF Jens Axboe
2023-01-09  3:51 ` Jens Axboe [this message]
2023-01-09  9:31 ` [PATCHv2 00/12] iov_iter: replace import_single_range with ubuf David Howells
2023-01-09 15:12   ` Keith Busch

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] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [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