public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [RFC 0/3] request parameter set api and wait termination tuning
Date: Sun, 10 Nov 2024 14:56:19 +0000	[thread overview]
Message-ID: <[email protected]> (raw)

A crude prototype for probing opinions on the API. Not suitable for
upstream in the current form. Not properly tested either.

Patch 1 adds indirection for new parameters and flags by allowing
the user to register a certain combination of them and requests to
refer to them an index passed in sqe->personality. The use case in
mind is the tuning wake ups and wait loop termination conditions.

Patch 3 is not complete, and I have doubts about the semantics of
Patch 2, but it showcases what/how the series is trying to target.
Note, these are made as hints and can be seamlessly deprecated and
removed from the kernel, in which case the user will get woken up
more often / earlier, which should be tolerated.

Jens Axboe (1):
  io_uring: add support for ignoring inline completions for waits

Pavel Begunkov (2):
  io_uring: introduce request parameter sets
  io_uring: allow waiting loop to ignore some CQEs

 include/linux/io_uring_types.h |  9 ++++
 include/uapi/linux/io_uring.h  | 14 ++++++
 io_uring/io_uring.c            | 91 +++++++++++++++++++++++-----------
 io_uring/msg_ring.c            |  1 +
 io_uring/net.c                 |  1 +
 io_uring/register.c            | 52 +++++++++++++++++++
 6 files changed, 139 insertions(+), 29 deletions(-)

-- 
2.46.0


             reply	other threads:[~2024-11-10 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 14:56 Pavel Begunkov [this message]
2024-11-10 14:56 ` [RFC 1/3] io_uring: introduce request parameter sets Pavel Begunkov
2024-11-10 14:56 ` [RFC 2/3] io_uring: add support for ignoring inline completions for waits Pavel Begunkov
2024-11-10 14:56 ` [RFC 3/3] io_uring: allow waiting loop to ignore some CQEs Pavel Begunkov

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