From: Gao Xiang <hsiangkao@redhat.com>
To: lampahome <pahome.chen@mirlab.org>
Cc: linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] Fwd: Any tools of f2fs to inspect infos?
Date: Wed, 1 Jul 2020 17:16:22 +0800 [thread overview]
Message-ID: <20200701091622.GA5411@xiangao.remote.csb> (raw)
In-Reply-To: <CAB3eZfsO0ZN_79oaFpooJ32WNZwwyaS4GBb+W6jR=buU-VczAA@mail.gmail.com>
(cc linux-f2fs-devel, Jaegeuk, Chao.
It'd be better to ask related people and cc the corresponding list.)
On Wed, Jul 01, 2020 at 03:29:41PM +0800, lampahome wrote:
> As title
>
> Any tools of f2fs to inspect like allocated segments, hot/warm/cold
> ratio, or gc is running?
>
> thx
_______________________________________________
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: Gao Xiang <hsiangkao@redhat.com>
To: lampahome <pahome.chen@mirlab.org>
Cc: linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
chao@kernel.org
Subject: Fwd: Any tools of f2fs to inspect infos?
Date: Wed, 1 Jul 2020 17:16:22 +0800 [thread overview]
Message-ID: <20200701091622.GA5411@xiangao.remote.csb> (raw)
In-Reply-To: <CAB3eZfsO0ZN_79oaFpooJ32WNZwwyaS4GBb+W6jR=buU-VczAA@mail.gmail.com>
(cc linux-f2fs-devel, Jaegeuk, Chao.
It'd be better to ask related people and cc the corresponding list.)
On Wed, Jul 01, 2020 at 03:29:41PM +0800, lampahome wrote:
> As title
>
> Any tools of f2fs to inspect like allocated segments, hot/warm/cold
> ratio, or gc is running?
>
> thx
next prev parent reply other threads:[~2020-07-01 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 7:29 Any tools of f2fs to inspect infos? lampahome
2020-07-01 9:16 ` Gao Xiang [this message]
2020-07-01 9:16 ` Fwd: " Gao Xiang
2020-07-01 16:08 ` [f2fs-dev] " Jaegeuk Kim
2020-07-01 16:08 ` Jaegeuk Kim
2020-07-02 3:00 ` [f2fs-dev] " lampahome
2020-07-02 3:00 ` lampahome
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=20200701091622.GA5411@xiangao.remote.csb \
--to=hsiangkao@redhat.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pahome.chen@mirlab.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.