From: Brian Norris <computersforpeace@gmail.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: "valent.turkovic@gmail.com" <valent.turkovic@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Tracking flash IO activity?
Date: Mon, 18 May 2015 10:57:02 -0700 [thread overview]
Message-ID: <20150518175702.GO11598@ld-irv-0074> (raw)
In-Reply-To: <CAFLxGvwrCO8BozRb3jkncWy+2w6y82zz+wtL2r_E9i3VT3N8HQ@mail.gmail.com>
On Sat, May 16, 2015 at 11:22:52PM +0200, Richard Weinberger wrote:
> On Sat, May 16, 2015 at 10:53 PM, Brian Norris
> <computersforpeace@gmail.com> wrote:
> > I don't know of any similar IO stats for MTDs, sorry.
>
> I wonder how hard it would be to integrate mtd into our current block IO stats.
> It mtd is too low level we could also do it with UBI.
I'm not sure if blk-io's iostats would be sufficiently informative for
MTD/UBI anyway. Wouldn't we care about at least one extra
non-block-device stat: the erase stats?
Also (and this may be more like what Valent is asking for, though he
mentions JFFS2, not UBIFS) is there a readily-available tool for reading
the erase counter information from a UBI volume?
Brian
next prev parent reply other threads:[~2015-05-18 17:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 20:21 Tracking flash IO activity? valent.turkovic
[not found] ` <CAAbfDBfXZCrRJ2M_MDGP8Pmo97tLiduYGHa2AdKasTya60e81A@mail.gmail.com>
2015-05-16 20:41 ` valent.turkovic
2015-05-16 20:53 ` Brian Norris
2015-05-16 21:18 ` valent.turkovic
2015-05-16 21:22 ` Richard Weinberger
2015-05-16 22:39 ` valent.turkovic
2015-05-18 13:35 ` valent.turkovic
2015-05-18 17:57 ` Brian Norris [this message]
2015-05-18 19:12 ` Richard Weinberger
2015-05-18 19:22 ` nick
2015-05-18 19:37 ` Richard Weinberger
2015-05-18 19:40 ` nick
2015-05-18 19:44 ` Richard Weinberger
2015-05-18 19:48 ` nick
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=20150518175702.GO11598@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
--cc=valent.turkovic@gmail.com \
/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