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] Followup io_uring pull for 6.1-rc2
Date: Sat, 22 Oct 2022 10:32:00 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

Was going to delay this one for the potential batch next week, but turns
out it's more convenient for the networking side to get this into -rc2
as it'll conflict with a patch going into net-next also adding a socket
bit. Jakub has signed off on the net change.

Currently the zero-copy has automatic fallback to normal transmit, and
it was decided that it'd be cleaner to return an error instead if the
socket type doesn't support it. It does work with UDP and TCP, it's more
of a future proofing kind of thing (eg for samba).

Please pull!


The following changes since commit 996d3efeb091c503afd3ee6b5e20eabf446fd955:

  io-wq: Fix memory leak in worker creation (2022-10-20 05:48:59 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/io_uring-6.1-2022-10-22

for you to fetch changes up to cc767e7c6913f770741d9fad1efa4957c2623744:

  io_uring/net: fail zc sendmsg when unsupported by socket (2022-10-22 08:43:03 -0600)

----------------------------------------------------------------
io_uring-6.1-2022-10-22

----------------------------------------------------------------
Pavel Begunkov (3):
      net: flag sockets supporting msghdr originated zerocopy
      io_uring/net: fail zc send when unsupported by socket
      io_uring/net: fail zc sendmsg when unsupported by socket

 include/linux/net.h | 1 +
 io_uring/net.c      | 4 ++++
 net/ipv4/tcp.c      | 1 +
 net/ipv4/udp.c      | 1 +
 4 files changed, 7 insertions(+)

-- 
Jens Axboe

             reply	other threads:[~2022-10-22 16:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-22 16:32 Jens Axboe [this message]
2022-10-23 17:18 ` [GIT PULL] Followup io_uring pull for 6.1-rc2 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