From: lizetao <[email protected]>
To: Pavel Begunkov <[email protected]>
Cc: Anuj Gupta <[email protected]>,
Kanchan Joshi <[email protected]>,
"[email protected]" <[email protected]>
Subject: RE: [PATCH 4/4] io_uring/rw: pre-mapped rw attributes
Date: Mon, 6 Jan 2025 11:13:59 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <ea95e358ce21fe69200df6a0b1e747b8817a6ec6.1735301337.git.asml.silence@gmail.com>
Hi,
> -----Original Message-----
> From: Pavel Begunkov <[email protected]>
> Sent: Monday, December 30, 2024 9:30 PM
> To: [email protected]
> Cc: [email protected]; Anuj Gupta <[email protected]>; Kanchan
> Joshi <[email protected]>
> Subject: [PATCH 4/4] io_uring/rw: pre-mapped rw attributes
>
> Instead of copy_from_user()'ing request attributes, allow it to be grabbwd
> from a registered pre-registered parameter region like we do with registered
> wait arguments.
>
> Suggested-by: Anuj Gupta <[email protected]>
> Signed-off-by: Pavel Begunkov <[email protected]>
> ---
> include/uapi/linux/io_uring.h | 4 +++-
> io_uring/rw.c | 19 ++++++++++++++-----
> 2 files changed, 17 insertions(+), 6 deletions(-)
>
> diff --git a/include/uapi/linux/io_uring.h b/include/uapi/linux/io_uring.h index
> 38f0d6b10eaf..ec6e6fd37d1c 100644
> --- a/include/uapi/linux/io_uring.h
> +++ b/include/uapi/linux/io_uring.h
> @@ -112,7 +112,9 @@ struct io_uring_sqe { };
>
> /* sqe->attr_type_mask flags */
> -#define IORING_RW_ATTR_FLAG_PI (1U << 0)
> +#define IORING_RW_ATTR_FLAG_PI (1UL << 0)
> +#define IORING_RW_ATTR_REGISTERED (1UL << 63)
Why use (1UL << 63) instead of (1UL << 1) here?
> +
> /* PI attribute information */
> struct io_uring_attr_pi {
> __u16 flags;
> diff --git a/io_uring/rw.c b/io_uring/rw.c index dc1acaf95db1..b1db4595788b
> 100644
> --- a/io_uring/rw.c
> +++ b/io_uring/rw.c
> @@ -271,10 +271,17 @@ static int io_prep_rw_pi(struct io_kiocb *req, struct
> io_rw *rw, int ddir,
> size_t pi_len;
> int ret;
>
> - if (copy_from_user(&__pi_attr, u64_to_user_ptr(attr_ptr),
> - sizeof(pi_attr)))
> - return -EFAULT;
> - pi_attr = &__pi_attr;
> + if (attr_type_mask & IORING_RW_ATTR_REGISTERED) {
> + pi_attr = io_args_get_ptr(&req->ctx->sqe_args, attr_ptr,
> + sizeof(pi_attr));
Here pi_attr is just pointer, so maybe sizeof(__pi_attr) or sizeof(struct io_uring_attr_pi) will be better.
> + if (IS_ERR(pi_attr))
> + return PTR_ERR(pi_attr);
> + } else {
> + if (copy_from_user(&__pi_attr, u64_to_user_ptr(attr_ptr),
> + sizeof(pi_attr)))
Just like above, shoule be sizeof(struct io_uring_attr_pi) here.
> + return -EFAULT;
> + pi_attr = &__pi_attr;
> + }
>
> if (pi_attr->rsvd)
> return -EINVAL;
> @@ -294,6 +301,8 @@ static int io_prep_rw_pi(struct io_kiocb *req, struct
> io_rw *rw, int ddir,
> return ret;
> }
>
> +#define IO_RW_ATTR_ALLOWED_MASK (IORING_RW_ATTR_FLAG_PI |
> +IORING_RW_ATTR_REGISTERED)
> +
> static int io_prep_rw(struct io_kiocb *req, const struct io_uring_sqe *sqe,
> int ddir, bool do_import)
> {
> @@ -332,7 +341,7 @@ static int io_prep_rw(struct io_kiocb *req, const struct
> io_uring_sqe *sqe,
> u64 attr_ptr;
>
> /* only PI attribute is supported currently */
> - if (attr_type_mask != IORING_RW_ATTR_FLAG_PI)
The comment needs to be adjusted.
> + if (attr_type_mask & IO_RW_ATTR_ALLOWED_MASK)
Here should be attr_type_mask & ~IO_RW_ATTR_ALLOWED_MASK ?
> return -EINVAL;
>
> attr_ptr = READ_ONCE(sqe->attr_ptr);
> --
> 2.47.1
>
--
Li Zetao
next prev parent reply other threads:[~2025-01-06 11:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 13:30 [RFC 0/4] pre-mapped rw attributes Pavel Begunkov
2024-12-30 13:30 ` [PATCH 1/4] io_uring: add structure for registered arguments Pavel Begunkov
2024-12-30 13:30 ` [PATCH 2/4] io_uring: add registered request arguments Pavel Begunkov
2025-01-06 11:33 ` lizetao
2025-01-06 16:40 ` Pavel Begunkov
2024-12-30 13:30 ` [PATCH 3/4] io_uring/rw: use READ_ONCE with rw attributes Pavel Begunkov
2024-12-30 13:30 ` [PATCH 4/4] io_uring/rw: pre-mapped " Pavel Begunkov
2025-01-06 11:13 ` lizetao [this message]
2025-01-06 16:53 ` Pavel Begunkov
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