From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: Jens Axboe <[email protected]>, [email protected]
Subject: [PATCH 0/8] for-next cleanups
Date: Tue, 11 Apr 2023 12:06:00 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
A random set of cleanups
Patches 1 and 2 address kernel test robot warnings.
Patches 3 and 4 add some extra lockdep checks
The rest are doing minor rsrc cleanups.
Pavel Begunkov (8):
io_uring: shut io_prep_async_work warning
io_uring/kbuf: remove extra ->buf_ring null check
io_uring: add irq lockdep checks
io_uring/rsrc: add lockdep checks
io_uring/rsrc: consolidate node caching
io_uring/rsrc: zero node's rsrc data on alloc
io_uring/rsrc: refactor io_rsrc_node_switch
io_uring/rsrc: extract SCM file put helper
include/linux/io_uring_types.h | 1 -
io_uring/alloc_cache.h | 5 +++
io_uring/io_uring.c | 9 ++---
io_uring/io_uring.h | 2 +
io_uring/kbuf.c | 14 +++----
io_uring/rsrc.c | 73 +++++++++++++++-------------------
io_uring/rsrc.h | 7 ++++
7 files changed, 56 insertions(+), 55 deletions(-)
--
2.40.0
next reply other threads:[~2023-04-11 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 11:06 Pavel Begunkov [this message]
2023-04-11 11:06 ` [PATCH 1/8] io_uring: shut io_prep_async_work warning Pavel Begunkov
2023-04-11 11:06 ` [PATCH 2/8] io_uring/kbuf: remove extra ->buf_ring null check Pavel Begunkov
2023-04-11 11:06 ` [PATCH 3/8] io_uring: add irq lockdep checks Pavel Begunkov
2023-04-11 11:06 ` [PATCH 4/8] io_uring/rsrc: add " Pavel Begunkov
2023-04-11 11:06 ` [PATCH 5/8] io_uring/rsrc: consolidate node caching Pavel Begunkov
2023-04-11 11:06 ` [PATCH 6/8] io_uring/rsrc: zero node's rsrc data on alloc Pavel Begunkov
2023-04-11 11:06 ` [PATCH 7/8] io_uring/rsrc: refactor io_rsrc_node_switch Pavel Begunkov
2023-04-11 11:06 ` [PATCH 8/8] io_uring/rsrc: extract SCM file put helper Pavel Begunkov
2023-04-12 18:10 ` [PATCH 0/8] for-next cleanups Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2021-10-23 11:13 Pavel Begunkov
2021-10-23 14:09 ` Jens Axboe
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