All of lore.kernel.org
 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 v5 2/2] f2fs: add ckpt_thread_ioprio sysfs node
Date: Fri, 22 Jan 2021 08:56:01 +0800	[thread overview]
Message-ID: <2e97b330-3e8d-d876-e060-e44123f27f2c@huawei.com> (raw)
In-Reply-To: <20210121134529.1201249-2-daeho43@gmail.com>

On 2021/1/21 21:45, 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>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,


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

WARNING: multiple messages have this Message-ID (diff)
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 v5 2/2] f2fs: add ckpt_thread_ioprio sysfs node
Date: Fri, 22 Jan 2021 08:56:01 +0800	[thread overview]
Message-ID: <2e97b330-3e8d-d876-e060-e44123f27f2c@huawei.com> (raw)
In-Reply-To: <20210121134529.1201249-2-daeho43@gmail.com>

On 2021/1/21 21:45, 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>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,

  reply	other threads:[~2021-01-22  0:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 13:45 [f2fs-dev] [PATCH v5 1/2] f2fs: introduce checkpoint=merge mount option Daeho Jeong
2021-01-21 13:45 ` Daeho Jeong
2021-01-21 13:45 ` [f2fs-dev] [PATCH v5 2/2] f2fs: add ckpt_thread_ioprio sysfs node Daeho Jeong
2021-01-21 13:45   ` Daeho Jeong
2021-01-22  0:56   ` Chao Yu [this message]
2021-01-22  0:56     ` [f2fs-dev] " Chao Yu
2021-01-22  0:55 ` [f2fs-dev] [PATCH v5 1/2] f2fs: introduce checkpoint=merge mount option Chao Yu
2021-01-22  0:55   ` Chao Yu
2021-01-22  1:36   ` Daeho Jeong
2021-01-22  1:36     ` Daeho Jeong
2021-01-22  1:46 ` Jaegeuk Kim
2021-01-22  1:46   ` Jaegeuk Kim
2021-01-22  1:56   ` Daeho Jeong
2021-01-22  1:56     ` Daeho Jeong

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=2e97b330-3e8d-d876-e060-e44123f27f2c@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.