From: Ming Lei <[email protected]>
To: Jens Axboe <[email protected]>,
[email protected], [email protected]
Cc: Gabriel Krisman Bertazi <[email protected]>,
Ming Lei <[email protected]>
Subject: [PATCH V4 0/2] io_uring: cancelable uring_cmd
Date: Sat, 23 Sep 2023 10:50:01 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
Hello,
Patch 1 retains top 8bits of uring_cmd flags for kernel internal use.
Patch 2 implements cancelable uring_cmd.
git tree(with ublk change)
https://github.com/ming1/linux/commits/uring_exit_and_ublk
V4:
- return -EINVAL in case that internal bits are set
- replace static lock checker with lockdep_assert_held(&ctx->uring_lock);
V3:
- code style change as suggested by Jens
- add patch 1
V2:
- use ->uring_cmd() with IO_URING_F_CANCEL for canceling command
Ming Lei (2):
io_uring: retain top 8bits of uring_cmd flags for kernel internal use
io_uring: cancelable uring_cmd
include/linux/io_uring.h | 19 +++++++++++++
include/linux/io_uring_types.h | 6 ++++
include/uapi/linux/io_uring.h | 5 ++--
io_uring/io_uring.c | 39 ++++++++++++++++++++++++++
io_uring/uring_cmd.c | 51 +++++++++++++++++++++++++++++++++-
5 files changed, 116 insertions(+), 4 deletions(-)
--
2.41.0
next reply other threads:[~2023-09-23 2:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 2:50 Ming Lei [this message]
2023-09-23 2:50 ` [PATCH V4 1/2] io_uring: retain top 8bits of uring_cmd flags for kernel internal use Ming Lei
2023-09-25 15:58 ` Gabriel Krisman Bertazi
[not found] ` <CGME20230928061733epcas5p1837b43637213341fb9674e99efa62a94@epcas5p1.samsung.com>
2023-09-28 6:11 ` Anuj Gupta
2023-09-23 2:50 ` [PATCH V4 2/2] io_uring: cancelable uring_cmd Ming Lei
2023-09-25 15:55 ` Gabriel Krisman Bertazi
2023-09-28 8:38 ` Jens Axboe
2023-09-28 8:55 ` Ming Lei
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] \
[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