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-final
Date: Fri, 30 Sep 2022 07:43:00 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

Two fixes that should go into 6.0:

- Tweak the single issuer logic to register the task at creation, rather
  than at first submit. SINGLE_ISSUER was added for 6.0, and after some
  discussion on this, we decided to make it a bit stricter while it's
  still possible to do so (Dylan).

- Stefan from Samba had some doubts on the level triggered poll that was
  added for this release. Rather than attempt to mess around with it
  now, just do the quick one-liner to disable it for release and we have
  time to discuss and change it for 6.1 instead (me).

Please pull!


The following changes since commit e775f93f2ab976a2cdb4a7b53063cbe890904f73:

  io_uring: ensure that cached task references are always put on exit (2022-09-23 18:51:08 -0600)

are available in the Git repository at:

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

for you to fetch changes up to d59bd748db0a97a5d6a33b284b6c58b7f6f4f768:

  io_uring/poll: disable level triggered poll (2022-09-28 19:27:11 -0600)

----------------------------------------------------------------
io_uring-6.0-2022-09-29

----------------------------------------------------------------
Dylan Yudaken (1):
      io_uring: register single issuer task at creation

Jens Axboe (1):
      io_uring/poll: disable level triggered poll

 io_uring/io_uring.c | 7 +++++++
 io_uring/poll.c     | 2 +-
 2 files changed, 8 insertions(+), 1 deletion(-)

-- 
Jens Axboe

             reply	other threads:[~2022-09-30 13:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 13:43 Jens Axboe [this message]
2022-09-30 16:38 ` [GIT PULL] io_uring fixes for 6.0-final 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