From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes
Date: Tue, 9 Nov 2021 10:06:34 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Minr fixes that should go into the 5.16 release:
- Fix max worker setting not working correctly on NUMA (Beld)
- Correctly return current setting for max workers if zeroes are passed
in (Pavel)
- io_queue_sqe_arm_apoll() cleanup, as identified during the initial
merge (Pavel)
- Misc fixes (Nghia, me)
Please pull!
The following changes since commit bfc484fe6abba4b89ec9330e0e68778e2a9856b2:
Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6 (2021-11-01 21:24:02 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/io_uring-5.16-2021-11-09
for you to fetch changes up to bad119b9a00019054f0c9e2045f312ed63ace4f4:
io_uring: honour zeroes as io-wq worker limits (2021-11-08 08:39:48 -0700)
----------------------------------------------------------------
io_uring-5.16-2021-11-09
----------------------------------------------------------------
Beld Zhang (1):
io-wq: fix max-workers not correctly set on multi-node system
Jens Axboe (1):
io_uring: remove dead 'sqe' store
Nghia Le (1):
io_uring: remove redundant assignment to ret in io_register_iowq_max_workers()
Pavel Begunkov (2):
io_uring: clean up io_queue_sqe_arm_apoll
io_uring: honour zeroes as io-wq worker limits
fs/io-wq.c | 16 +++++++++++++---
fs/io_uring.c | 11 ++++-------
2 files changed, 17 insertions(+), 10 deletions(-)
--
Jens Axboe
next reply other threads:[~2021-11-09 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 17:06 Jens Axboe [this message]
2021-11-09 19:31 ` [GIT PULL] io_uring fixes 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