From: Chao Yu <chao@kernel.org>
To: Zhiguo Niu <zhiguo.niu@unisoc.com>, jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, niuzhiguo84@gmail.com,
ke.wang@unisoc.com
Subject: Re: [PATCH] f2fs: use new ioprio Macro to get ckpt thread ioprio data
Date: Mon, 3 Jun 2024 14:39:53 +0800 [thread overview]
Message-ID: <b0c9f3dc-417a-4891-bdf0-25b849828e3b@kernel.org> (raw)
In-Reply-To: <1717146645-18829-1-git-send-email-zhiguo.niu@unisoc.com>
On 2024/5/31 17:10, Zhiguo Niu wrote:
> Use new Macro IOPRIO_PRIO_LEVEL to get ckpt thread ioprio data(level),
> it is more accurate and consisten with the way setting ckpt thread
> ioprio(IOPRIO_PRIO_VALUE(class, data)).
>
> Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.com>
> ---
> fs/f2fs/sysfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/sysfs.c b/fs/f2fs/sysfs.c
> index 72676c5..55d46da 100644
> --- a/fs/f2fs/sysfs.c
> +++ b/fs/f2fs/sysfs.c
> @@ -340,7 +340,7 @@ static ssize_t f2fs_sbi_show(struct f2fs_attr *a,
> if (!strcmp(a->attr.name, "ckpt_thread_ioprio")) {
> struct ckpt_req_control *cprc = &sbi->cprc_info;
> int class = IOPRIO_PRIO_CLASS(cprc->ckpt_thread_ioprio);
> - int data = IOPRIO_PRIO_DATA(cprc->ckpt_thread_ioprio);
> + int data = IOPRIO_PRIO_LEVEL(cprc->ckpt_thread_ioprio);
So, can you please use 'level' to instead 'data' in f2fs_sbi_show() and
__sbi_store()?
Thanks,
>
> if (class != IOPRIO_CLASS_RT && class != IOPRIO_CLASS_BE)
> return -EINVAL;
next prev parent reply other threads:[~2024-06-03 6:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 9:10 [PATCH] f2fs: use new ioprio Macro to get ckpt thread ioprio data Zhiguo Niu
2024-06-03 6:39 ` Chao Yu [this message]
2024-06-03 6:52 ` Zhiguo Niu
2024-06-03 7:50 ` Chao Yu
2024-06-03 8:14 ` Zhiguo Niu
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 \
--in-reply-to=b0c9f3dc-417a-4891-bdf0-25b849828e3b@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=ke.wang@unisoc.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=niuzhiguo84@gmail.com \
--cc=zhiguo.niu@unisoc.com \
/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