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]>,
	netdev <[email protected]>, Breno Leitao <[email protected]>
Subject: [GIT PULL] io_uring support for get/setsockopt
Date: Mon, 30 Oct 2023 08:36:04 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

On top of the core io_uring changes, this pull request adds support for
using getsockopt and setsockopt via io_uring. The main use cases for
this is to enable use of direct descriptors, rather than first
instantiating a normal file descriptor, doing the option tweaking
needed, then turning it into a direct descriptor. With this support, we
can avoid needing a regular file descriptor completely.

The net and bpf bits have been signed off on their side.

Please pull!


The following changes since commit 6ce4a93dbb5bd93bc2bdf14da63f9360a4dcd6a1:

  io_uring/poll: use IOU_F_TWQ_LAZY_WAKE for wakeups (2023-10-19 06:42:29 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/for-6.7/io_uring-sockopt-2023-10-30

for you to fetch changes up to b9ec913212e6e91efa5a0a612c4a8ec4cf5da896:

  selftests/bpf/sockopt: Add io_uring support (2023-10-19 16:42:04 -0600)

----------------------------------------------------------------
for-6.7/io_uring-sockopt-2023-10-30

----------------------------------------------------------------
Breno Leitao (11):
      bpf: Add sockptr support for getsockopt
      bpf: Add sockptr support for setsockopt
      net/socket: Break down __sys_setsockopt
      net/socket: Break down __sys_getsockopt
      io_uring/cmd: Pass compat mode in issue_flags
      tools headers: Grab copy of io_uring.h
      selftests/net: Extract uring helpers to be reusable
      io_uring/cmd: return -EOPNOTSUPP if net is disabled
      io_uring/cmd: Introduce SOCKET_URING_OP_GETSOCKOPT
      io_uring/cmd: Introduce SOCKET_URING_OP_SETSOCKOPT
      selftests/bpf/sockopt: Add io_uring support

 include/linux/bpf-cgroup.h                         |   9 +-
 include/linux/io_uring.h                           |   1 +
 include/net/sock.h                                 |   6 +-
 include/uapi/linux/io_uring.h                      |   8 +
 io_uring/uring_cmd.c                               |  53 ++
 kernel/bpf/cgroup.c                                |  25 +-
 net/core/sock.c                                    |   8 -
 net/socket.c                                       | 104 ++-
 tools/include/io_uring/mini_liburing.h             | 282 ++++++++
 tools/include/uapi/linux/io_uring.h                | 757 +++++++++++++++++++++
 tools/testing/selftests/bpf/prog_tests/sockopt.c   | 113 ++-
 tools/testing/selftests/net/Makefile               |   1 +
 tools/testing/selftests/net/io_uring_zerocopy_tx.c | 268 +-------
 13 files changed, 1301 insertions(+), 334 deletions(-)
 create mode 100644 tools/include/io_uring/mini_liburing.h
 create mode 100644 tools/include/uapi/linux/io_uring.h

-- 
Jens Axboe


             reply	other threads:[~2023-10-30 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 14:36 Jens Axboe [this message]
2023-11-01 22:47 ` [GIT PULL] io_uring support for get/setsockopt pr-tracker-bot
2023-11-02  5:01 ` patchwork-bot+netdevbpf

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] \
    /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