From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring followup updates for 6.2-rc1
Date: Sat, 10 Dec 2022 08:36:00 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
As mentioned, here are the followup changes for io_uring. This branch
only exists to avoid the poll related conflicts that would've otherwise
arised without the split.
This pull request contains:
- Misc fixes (me, Lin)
- Series from Pavel extending the single task exclusive ring mode,
yielding nice improvements for the common case of having a single ring
per thread (Pavel)
- Cleanup for MSG_RING, removing our IOPOLL hack (Pavel)
- Further poll cleanups and fixes (Pavel)
- Misc cleanups and fixes (Pavel)
Please pull!
The following changes since commit b7b275e60bcd5f89771e865a8239325f86d9927d:
Linux 6.1-rc7 (2022-11-27 13:31:48 -0800)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/for-6.2/io_uring-next-2022-12-08
for you to fetch changes up to 761c61c15903db41343532882b0443addb8c2faf:
io_uring/msg_ring: flag target ring as having task_work, if needed (2022-12-08 09:36:02 -0700)
----------------------------------------------------------------
for-6.2/io_uring-next-2022-12-08
----------------------------------------------------------------
Jens Axboe (2):
Merge branch 'for-6.2/io_uring' into for-6.2/io_uring-next
io_uring/msg_ring: flag target ring as having task_work, if needed
Lin Ma (2):
io_uring/poll: remove outdated comments of caching
io_uring: update outdated comment of callbacks
Pavel Begunkov (21):
io_uring: kill io_poll_issue's PF_EXITING check
io_uring: carve io_poll_check_events fast path
io_uring: remove ctx variable in io_poll_check_events
io_uring: improve poll warning handling
io_uring: combine poll tw handlers
io_uring: don't raw spin unlock to match cq_lock
io_uring: improve rsrc quiesce refs checks
io_uring: don't reinstall quiesce node for each tw
io_uring: reshuffle issue_flags
io_uring: dont remove file from msg_ring reqs
io_uring: improve io_double_lock_ctx fail handling
io_uring: skip overflow CQE posting for dying ring
io_uring: don't check overflow flush failures
io_uring: complete all requests in task context
io_uring: force multishot CQEs into task context
io_uring: use tw for putting rsrc
io_uring: never run tw and fallback in parallel
io_uring: get rid of double locking
io_uring: extract a io_msg_install_complete helper
io_uring: do msg_ring in target task via tw
io_uring: skip spinlocking for ->task_complete
include/linux/io_uring.h | 13 +--
include/linux/io_uring_types.h | 3 +
io_uring/io_uring.c | 167 ++++++++++++++++++++++-----------
io_uring/io_uring.h | 15 ++-
io_uring/msg_ring.c | 164 ++++++++++++++++++++++----------
io_uring/msg_ring.h | 1 +
io_uring/net.c | 21 +++++
io_uring/opdef.c | 8 ++
io_uring/opdef.h | 2 +
io_uring/poll.c | 98 +++++++++----------
io_uring/rsrc.c | 72 ++++++++------
io_uring/rsrc.h | 1 +
12 files changed, 369 insertions(+), 196 deletions(-)
--
Jens Axboe
next reply other threads:[~2022-12-10 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 15:36 Jens Axboe [this message]
2022-12-13 19:02 ` [GIT PULL] io_uring followup updates for 6.2-rc1 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