linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Daeho Jeong <daeho43@gmail.com>, <linux-kernel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>,
	<kernel-team@android.com>
Cc: Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH v2 2/2] f2fs: add ckpt_thread_ioprio sysfs node
Date: Thu, 21 Jan 2021 18:30:22 +0800	[thread overview]
Message-ID: <d4c12d47-db33-7e76-b7ad-4d80ced1aba9@huawei.com> (raw)
In-Reply-To: <20210114062302.3809664-2-daeho43@gmail.com>

On 2021/1/14 14:23, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
> 
> Added "ckpt_thread_ioprio" sysfs node to give a way to change checkpoint
> merge daemon's io priority. Its default value is "be,3", which means
> "BE" I/O class and I/O priority "3". We can select the class between "rt"
> and "be", and set the I/O priority within valid range of it.
> "," delimiter is necessary in between I/O class and priority number.
> 
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> ---
> v2:
> - adapt to inlining ckpt_req_control of f2fs_sb_info
> ---
>   Documentation/ABI/testing/sysfs-fs-f2fs |  8 ++++
>   fs/f2fs/checkpoint.c                    |  2 +-
>   fs/f2fs/f2fs.h                          |  1 +
>   fs/f2fs/sysfs.c                         | 51 +++++++++++++++++++++++++
>   4 files changed, 61 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/ABI/testing/sysfs-fs-f2fs b/Documentation/ABI/testing/sysfs-fs-f2fs
> index 3dfee94e0618..0c48b2e7dfd4 100644
> --- a/Documentation/ABI/testing/sysfs-fs-f2fs
> +++ b/Documentation/ABI/testing/sysfs-fs-f2fs
> @@ -377,3 +377,11 @@ Description:	This gives a control to limit the bio size in f2fs.
>   		Default is zero, which will follow underlying block layer limit,
>   		whereas, if it has a certain bytes value, f2fs won't submit a
>   		bio larger than that size.
> +What:		/sys/fs/f2fs/<disk>/ckpt_thread_ioprio
> +Date:		January 2021
> +Contact:	"Daeho Jeong" <daehojeong@google.com>
> +Description:	Give a way to change checkpoint merge daemon's io priority.
> +		Its default value is "be,3", which means "BE" I/O class and
> +		I/O priority "3". We can select the class between "rt" and "be",
> +		and set the I/O priority within valid range of it. "," delimiter
> +		is necessary in between I/O class and priority number.
> diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
> index e0668cec3b80..62bd6f449bb7 100644
> --- a/fs/f2fs/checkpoint.c
> +++ b/fs/f2fs/checkpoint.c
> @@ -1840,7 +1840,7 @@ int f2fs_start_ckpt_thread(struct f2fs_sb_info *sbi)
>   	if (IS_ERR(cprc->f2fs_issue_ckpt))
>   		return PTR_ERR(cprc->f2fs_issue_ckpt);
>   
> -	set_task_ioprio(cprc->f2fs_issue_ckpt, DEFAULT_CHECKPOINT_IOPRIO);
> +	set_task_ioprio(cprc->f2fs_issue_ckpt, cprc->ckpt_thread_ioprio);

Where do we set default value of cprc->ckpt_thread_ioprio? I guess it should
be f2fs_init_ckpt_req_control()?

Thanks,


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2021-01-21 10:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14  6:23 [f2fs-dev] [PATCH v2 1/2] f2fs: introduce checkpoint=merge mount option Daeho Jeong
2021-01-14  6:23 ` [f2fs-dev] [PATCH v2 2/2] f2fs: add ckpt_thread_ioprio sysfs node Daeho Jeong
2021-01-21 10:30   ` Chao Yu [this message]
2021-01-21 10:57     ` Daeho Jeong
2021-01-15  9:22 ` [f2fs-dev] [PATCH v2 1/2] f2fs: introduce checkpoint=merge mount option Chao Yu
2021-01-15 14:00   ` Daeho Jeong
2021-01-15 14:23     ` Daeho Jeong
2021-01-15 14:33     ` Chao Yu

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=d4c12d47-db33-7e76-b7ad-4d80ced1aba9@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=daeho43@gmail.com \
    --cc=daehojeong@google.com \
    --cc=kernel-team@android.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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).