From: Zhiguo Niu <niuzhiguo84@gmail.com>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, ke.wang@unisoc.com,
Zhiguo Niu <zhiguo.niu@unisoc.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: use new ioprio Macro to get ckpt thread ioprio data
Date: Mon, 3 Jun 2024 16:14:38 +0800 [thread overview]
Message-ID: <CAHJ8P3LVadqmrFsZLcbCp_QdCo06F2YtpgfL0hrVrrp6fdyrnA@mail.gmail.com> (raw)
In-Reply-To: <10f4898f-0b8c-4503-8620-3bb566e9a163@kernel.org>
On Mon, Jun 3, 2024 at 3:50 PM Chao Yu <chao@kernel.org> wrote:
>
> On 2024/6/3 14:52, Zhiguo Niu wrote:
> > On Mon, Jun 3, 2024 at 2:39 PM Chao Yu <chao@kernel.org> wrote:
> >>
> >> 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()?
> > Hi Chao,
> >
> > IOPRIO_PRIO_DATA in the new kernel version includes two parts: level and hint.
> > In __sbi_store, " IOPRIO_PRIO_VALUE(class, data)" is used to set ckpt
> > iopriority,
> > and it will pass default hint value, we just need to keep class /level right.
>
> Zhiguo,
>
> I think f2fs only support configuring priolevel rather than priolevel and
> priohint of ckpt thread via ckpt_thread_ioprio sysfs interface, so it will
> be more readable to use 'level' instead of 'data' in context of the interface,
> thoughts?
Hi Chao,
I understand what you said and I agree with this. I will update it in
the next version.
Thanks!
>
> Thanks,
>
> >
> > #define IOPRIO_PRIO_VALUE(prioclass, priolevel) \
> > ioprio_value(prioclass, priolevel, IOPRIO_HINT_NONE)
> > so i think this part is not needed to modify.
> >
> > thanks!
> >>
> >> Thanks,
> >>
> >>>
> >>> if (class != IOPRIO_CLASS_RT && class != IOPRIO_CLASS_BE)
> >>> return -EINVAL;
> >>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2024-06-03 8:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 9:10 [f2fs-dev] [PATCH] f2fs: use new ioprio Macro to get ckpt thread ioprio data Zhiguo Niu
2024-06-03 6:39 ` Chao Yu
2024-06-03 6:52 ` Zhiguo Niu
2024-06-03 7:50 ` Chao Yu
2024-06-03 8:14 ` Zhiguo Niu [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 \
--in-reply-to=CAHJ8P3LVadqmrFsZLcbCp_QdCo06F2YtpgfL0hrVrrp6fdyrnA@mail.gmail.com \
--to=niuzhiguo84@gmail.com \
--cc=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=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;
as well as URLs for NNTP newsgroup(s).