linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: 李扬韬 <frank.li@vivo.com>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: add sysfs nodes to get discard information
Date: Mon, 16 Aug 2021 17:16:24 -0700	[thread overview]
Message-ID: <YRr/2DM84TishToA@google.com> (raw)
In-Reply-To: <AGwAWQBVD3NfsYDCdBIWb4qP.3.1629094420548.Hmail.frank.li@vivo.com>

On 08/16, 李扬韬 wrote:
> >>>> I've added new sysfs nodes to show discard stat since mount, which
> >>>> will help us analyze whether the performance problem is related to
> >>>> discard.
> >>>>
> >>>> issued_discard  - Shows the number of issued discard
> >>>> queued_discard  - Shows the number of cached discard cmd count
> >>>> discard_cmd_cnt - Shows the number of cached discard cmd count
> >>>> undiscard_blks  - Shows the number of undiscard blocks
> >>>
> >>> We have exported them in debugfs, can you use that?
> >>>
> >>> Thanks,
> >> 
> >> But now Android is forbidden to open debugfs, and in fact we have not
> >> opened this configuration for a long time.
> >
> >Weren't them be used for debug purpose? can you please explain more about
> >your use case?
> 
> During long-term aging test or normal use, sometimes there will be performance
> degradation problems. It may be caused by storage, or it may be caused by the
> filesystem. For example, the filesystem accumulates a large number of undiscard
>  blocks. Although there is some remaining space, the androidbench test will
> show performance degradation. Therefore, it is necessary to export information
> related to discard so that we can confirm this situation.

I think you can mount debugfs for that case?

> 
> Thx,
> 
> 


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

  reply	other threads:[~2021-08-17  0:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-14 17:58 [f2fs-dev] [PATCH 1/2] f2fs: add sysfs nodes to get discard information Yangtao Li
2021-08-14 17:58 ` [f2fs-dev] [PATCH 2/2] f2fs: fix description about main_blkaddr node Yangtao Li
2021-08-16  2:37   ` Chao Yu
2021-08-16  2:35 ` [f2fs-dev] [PATCH 1/2] f2fs: add sysfs nodes to get discard information Chao Yu
2021-08-16  2:42   ` 李扬韬
2021-08-16  4:15     ` Chao Yu
2021-08-16  6:13       ` 李扬韬
2021-08-17  0:16         ` Jaegeuk Kim [this message]
2021-08-19  4:49         ` 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=YRr/2DM84TishToA@google.com \
    --to=jaegeuk@kernel.org \
    --cc=frank.li@vivo.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).