From: nick <xerofoify@gmail.com>
To: Richard Weinberger <richard@nod.at>,
Brian Norris <computersforpeace@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 15:22:41 -0400 [thread overview]
Message-ID: <555A3C01.3030800@gmail.com> (raw)
In-Reply-To: <555A398B.8050203@nod.at>
On 2015-05-18 03:12 PM, Richard Weinberger wrote:
> Am 18.05.2015 um 19:57 schrieb Brian Norris:
>> 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?
>
> This coin has two sides.
> I agree that for MTD we have three interesting counters, read, write and erase
> which would deserve their own tool. Maybe something like mtdtop or mtdstat?
> But it would be nice if well known tools like iostat(1) could work too.
>
>> 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?
>
> Not really. I have a very hacky tool to inspect UBI Images.
> Mainly to debug fastmap issues. If I find some spare time to
> polish it I'll happily publish it.
>
> Thanks,
> //richard
>
Richard,
I feel that not having a tool like this is a very bad idea, it
may be one of the major issues I or others may have with ubifs
as a file system choice for flash based systems. You stated that
the tool you have is hacky, does this mean in terms of bugs or
coding standards? If the tool works and is fairly stable why not
push to the repo for mtd-tools and mark it as experimental for now.
This way the mtd developers can start working on it and allow you
time to do other more important things with your time as a maintainer.
Nick
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
next prev parent reply other threads:[~2015-05-18 19:23 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
2015-05-18 19:12 ` Richard Weinberger
2015-05-18 19:22 ` nick [this message]
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=555A3C01.3030800@gmail.com \
--to=xerofoify@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--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