From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: introduce data read/write showing path info
Date: Tue, 29 Mar 2022 11:09:40 -0700 [thread overview]
Message-ID: <YkNLZPRMDwmVml1w@google.com> (raw)
In-Reply-To: <101f4cb6-37bf-0ac3-3838-7aab7e648352@kernel.org>
On 03/29, Chao Yu wrote:
> On 2022/3/29 11:13, Jaegeuk Kim wrote:
> > This was used in Android for a long time. Let's upstream it.
>
> Could you please explain more about its usage?
I found ioblame and ioshark in android are using it to understand app/file/IO
traffic. Once we have this in AOSP, I'm thinking to change one by one.
The android-mainline is also deprecating the custom tracepoints as well.
https://android-review.googlesource.com/c/kernel/common/+/2045529
>
> >
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
>
> The code part looks clean.
>
> Reviewed-by: Chao Yu <chao@kernel.org>
>
> 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:[~2022-03-29 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 22:33 [f2fs-dev] [PATCH] f2fs: introduce data read/write showing path info Jaegeuk Kim
2022-03-21 22:41 ` Eric Biggers
2022-03-22 0:14 ` Jaegeuk Kim
2022-03-22 0:13 ` [f2fs-dev] [PATCH v2] " Jaegeuk Kim
2022-03-29 3:04 ` Chao Yu
2022-03-29 3:13 ` [f2fs-dev] [PATCH v3] " Jaegeuk Kim
2022-03-29 14:23 ` Chao Yu
2022-03-29 18:09 ` Jaegeuk Kim [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=YkNLZPRMDwmVml1w@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--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).