From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>,
<kernel-team@android.com>
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: add tracepoint for f2fs iostat
Date: Thu, 16 Apr 2020 14:55:54 +0800 [thread overview]
Message-ID: <0a821dfb-f2fc-649b-617d-27c1d5ca599b@huawei.com> (raw)
In-Reply-To: <20200416034217.GA254838@google.com>
On 2020/4/16 11:42, Jaegeuk Kim wrote:
> v2:
> - add sysfs entry to give the time period
> - keep stat records in sbi
>
>>From 805015f3f2cec3acf43321359129c5382a1d5db4 Mon Sep 17 00:00:00 2001
> From: Daeho Jeong <daehojeong@google.com>
> Date: Mon, 30 Mar 2020 03:30:59 +0000
> Subject: [PATCH] f2fs: add tracepoint for f2fs iostat
>
> Added a tracepoint to see iostat of f2fs. Default period of that
> is 3 second. This tracepoint can be used to be monitoring
> I/O statistics periodically.
>
> Bug: 152162885
> Change-Id: I6fbe010b9cf1a90caa0f4793a6dab77c4cba7da6
Should be removed...
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
Otherwise, it looks good to me.
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
prev parent reply other threads:[~2020-04-16 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 16:16 [f2fs-dev] [PATCH] f2fs: add tracepoint for f2fs iostat Jaegeuk Kim
2020-04-15 6:23 ` Chao Yu
2020-04-15 20:56 ` Jaegeuk Kim
2020-04-16 3:42 ` [f2fs-dev] [PATCH v2] " Jaegeuk Kim
2020-04-16 6:55 ` Chao Yu [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=0a821dfb-f2fc-649b-617d-27c1d5ca599b@huawei.com \
--to=yuchao0@huawei.com \
--cc=jaegeuk@kernel.org \
--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).