public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Bruce_Leonard@selinc.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: MTD/flash perfomance statistics
Date: Tue, 18 Nov 2008 10:05:09 +0200	[thread overview]
Message-ID: <1226995509.16925.115.camel@sauron> (raw)
In-Reply-To: <OFE19505F1.464981E8-ON88257504.0081B596-88257504.00822E2D@selinc.com>

On Mon, 2008-11-17 at 15:42 -0800, Bruce_Leonard@selinc.com wrote:
> "They appear to be going the wrong way.  We're looking for runtime 
> diagnostic-y type of things (i.e. Number of writes to the flash, number of 
> bad blocks, statistics from the wear leveler to see how the wear leveling 
> is going, etc.)  Things that don't take a lot of CPU time to do, like 
> counters, that we can use to give us information on what a customer's box 
> may or may not be doing in the field.  A ready example that comes to mind 
> is ethernet statistics, bytes/packets sent/recieved, error counts, etc. Or 
> if you want a storage analog, things like you would see in 
> /sys/block/hda/stat but adapted to make sense in Flash storage."

I see. No, we do not really provide this statistics, just because no one
needed this. Please, give me the list of what exactly you would like to
know, and I will try to implement this for you.

> BTW, we're happily up and running UBIFS on a 2GiB flash part with no 
> errors.  Mount times are pretty resonable.  I don't have current times 
> because I've been about three kernel versions ahead of everyone else so 
> the stuff they've all been using until recently didn't have some of the 
> speed improvments.  If I get the time (and remember to do it ;)  ) I'll 
> try to float some numbers out there.

Cool, of course numbers and hardware information (CPU, flash type, I/O
speed) is appreciated.

> Thanks for all the help over the last several months getting my stuff 
> going.  It's been great working with you.

No problem.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2008-11-18  8:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 18:08 MTD/flash perfomance statistics Bruce_Leonard
2008-11-12  5:38 ` Artem Bityutskiy
2008-11-12  8:30   ` Bruce_Leonard
2008-11-17 23:42   ` Bruce_Leonard
2008-11-18  8:05     ` Artem Bityutskiy [this message]
2008-11-21 18:41       ` Bruce_Leonard
2008-12-02  9:26         ` Artem Bityutskiy

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=1226995509.16925.115.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=Bruce_Leonard@selinc.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