public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Stefan Roesch <[email protected]>,
	[email protected], [email protected],
	[email protected]
Cc: [email protected]
Subject: Re: [PATCH v4 5/5] io_uring: add fgetxattr and getxattr support
Date: Tue, 21 Dec 2021 17:32:35 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 12/15/21 22:17, Stefan Roesch wrote:
> This adds support to io_uring for the fgetxattr and getxattr API.

Same comments as with 4/5, only one additional below

> 
> Signed-off-by: Stefan Roesch <[email protected]>
> ---
>   fs/io_uring.c                 | 150 ++++++++++++++++++++++++++++++++++
>   include/uapi/linux/io_uring.h |   2 +
>   2 files changed, 152 insertions(+)
> 
> diff --git a/fs/io_uring.c b/fs/io_uring.c
> index fc2239635342..c365944a8054 100644
> --- a/fs/io_uring.c
> +++ b/fs/io_uring.c
[...]
> diff --git a/include/uapi/linux/io_uring.h b/include/uapi/linux/io_uring.h
> index dbf473900da2..cd9160272308 100644
> --- a/include/uapi/linux/io_uring.h
> +++ b/include/uapi/linux/io_uring.h
> @@ -145,7 +145,9 @@ enum {
>   	IORING_OP_MKDIRAT,
>   	IORING_OP_SYMLINKAT,
>   	IORING_OP_LINKAT,
> +	IORING_OP_FGETXATTR,

Even though it's just one-commit gap, it's not great changing uapi,
e.g. +1 to previous IORING_OP_FSETXATTR. It may actually make more
sense to keep xget and xfget closer together because you're reusing
code for them and compiler may _potentially_ better optimise it,
e.g. ifs in switches.

>   	IORING_OP_FSETXATTR,
> +	IORING_OP_GETXATTR,
>   	IORING_OP_SETXATTR,
>   
>   	/* this goes last, obviously */

-- 
Pavel Begunkov

      reply	other threads:[~2021-12-21 17:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 22:16 [PATCH v4 0/5] io_uring: add xattr support Stefan Roesch
2021-12-15 22:16 ` [PATCH v4 1/5] fs: split off do_user_path_at_empty from user_path_at_empty() Stefan Roesch
2021-12-15 22:16 ` [PATCH v4 2/5] fs: split off setxattr_setup function from setxattr Stefan Roesch
2021-12-15 22:17 ` [PATCH v4 3/5] fs: split off do_getxattr from getxattr Stefan Roesch
2021-12-15 22:17 ` [PATCH v4 4/5] io_uring: add fsetxattr and setxattr support Stefan Roesch
2021-12-21 17:27   ` Pavel Begunkov
2021-12-15 22:17 ` [PATCH v4 5/5] io_uring: add fgetxattr and getxattr support Stefan Roesch
2021-12-21 17:32   ` Pavel Begunkov [this message]

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] \
    [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