Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Folkert van Heusden <folkert.van.heusden@gmail.com>,
	linux-mtd@lists.infradead.org
Subject: Re: measuring the flash usage
Date: Wed, 21 Sep 2011 09:27:57 +0300	[thread overview]
Message-ID: <1316586484.4849.79.camel@sauron> (raw)
In-Reply-To: <CAN8TOE8s-DbYNWuDht0KhU3wbW-4owNHxgvv-m_mftRReUzhRg@mail.gmail.com>

On Tue, 2011-09-20 at 14:02 -0700, Brian Norris wrote:
> Hi,
> 
> On Tue, Sep 20, 2011 at 4:22 AM, Folkert van Heusden
> <folkert.van.heusden@gmail.com> wrote:
> > For an embedded system I'm working on I'd like to monitor the health
> > of the flash memory.
> > On regular Linux systems one can look at /proc/diskstats to see how
> > often the system writes to a disk. It seems though that (at least
> > kernel 2.6.19) for flash these counters are not updated.
> 
> I don't have much experience with the /proc/diskstats but for me, it
> at least lists the mtdblockX devices I have on my system (which I
> don't use).

That will only account I/O via mtdblock, but not via mtd devices.

I think we do not have proper I/O accounting for MTD. In N900 we hacked
/proc/diskstats to also show MTD I/O, but for some reasons (do not
remember) we decided that would not be upstreamable. You can try that,
or introduce mtd-specific sysfs entries for accounting.


-- 
Best Regards,
Artem Bityutskiy

  reply	other threads:[~2011-09-21  6:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20 11:22 measuring the flash usage Folkert van Heusden
2011-09-20 21:02 ` Brian Norris
2011-09-21  6:27   ` Artem Bityutskiy [this message]
2011-09-21  6:47   ` Folkert van Heusden
2011-09-21 19:04     ` Brian Norris

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=1316586484.4849.79.camel@sauron \
    --to=dedekind1@gmail.com \
    --cc=computersforpeace@gmail.com \
    --cc=folkert.van.heusden@gmail.com \
    --cc=linux-mtd@lists.infradead.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