public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.0-rc4
Date: Fri, 2 Sep 2022 10:37:32 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

Two parts in this pull request:

- Single fix for over-eager retries for networking (Pavel)

- Revert of the notification slot support for zerocopy sends. Turns out
  that even after more than a year or development and testing, there's
  not full agreement on whether just using plain ordered notifications
  is Good Enough to avoid the complexity of using the notifications
  slots. Because of that, we decided that it's best left to a future
  final decision. We can always bring back this feature, but we can't
  really change it or remove it once we've released 6.0 with it enabled.
  The reverts leave the usual CQE notifications as the primary interface
  for knowing when data was sent, and when it was acked. (Pavel)

Please pull!


The following changes since commit 581711c46612c1fd7f98960f9ad53f04fdb89853:

  io_uring/net: save address for sendzc async execution (2022-08-25 07:52:30 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux-block.git tags/io_uring-6.0-2022-09-02

for you to fetch changes up to 916d72c10a4ca80ea51f1421e774cb765b53f28f:

  selftests/net: return back io_uring zc send tests (2022-09-01 09:13:33 -0600)

----------------------------------------------------------------
io_uring-6.0-2022-09-02

----------------------------------------------------------------
Pavel Begunkov (7):
      io_uring/net: fix overexcessive retries
      selftests/net: temporarily disable io_uring zc test
      Revert "io_uring: add zc notification flush requests"
      Revert "io_uring: rename IORING_OP_FILES_UPDATE"
      io_uring/notif: remove notif registration
      io_uring/net: simplify zerocopy send user API
      selftests/net: return back io_uring zc send tests

 include/uapi/linux/io_uring.h                      |  28 ++----
 io_uring/io_uring.c                                |  14 +--
 io_uring/net.c                                     |  59 +++++++-----
 io_uring/net.h                                     |   1 +
 io_uring/notif.c                                   |  83 +----------------
 io_uring/notif.h                                   |  54 +----------
 io_uring/opdef.c                                   |  12 +--
 io_uring/rsrc.c                                    |  55 +----------
 io_uring/rsrc.h                                    |   4 +-
 tools/testing/selftests/net/io_uring_zerocopy_tx.c | 101 ++++++++-------------
 .../testing/selftests/net/io_uring_zerocopy_tx.sh  |  10 +-
 11 files changed, 99 insertions(+), 322 deletions(-)

-- 
Jens Axboe

             reply	other threads:[~2022-09-02 16:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02 16:37 Jens Axboe [this message]
2022-09-02 23:48 ` [GIT PULL] io_uring fixes for 6.0-rc4 pr-tracker-bot

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