public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Konstantin Kletschke <lists@ku-gbr.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: General performance of NAND operations i.e mount and ls
Date: Thu, 06 Sep 2007 14:11:59 +0300	[thread overview]
Message-ID: <1189077119.14370.52.camel@sauron> (raw)
In-Reply-To: <1189069864.14370.34.camel@sauron>

On Thu, 2007-09-06 at 12:11 +0300, Artem Bityutskiy wrote:

> > Okay, I wanted to check if the time is okay for 520MHz core with 104MHz
> > Bus and 8Bit flash. If this is the case my Hardware driver is okay.
> > There is no urge to improve this stat() time and fragtree building at
> > the moment. If it takes so long and the driver is okay it wioll take so
> > long (arguing with boss and customers :-)).
> 
> Try to measure raw R/W, e.g with dd. But beware dd will fail at the
> first met bad block. Something like:
> 
> Read: dd if=/dev/mtd4 of=/dev/null bs=4096 count=512
> Write: dd if=/dev/zero of=/dev/mtd4 bs=4096 count=512
> 
> It'll print raw R/W speed.  But beware dd will fail at the first bad
> block, so yo may have to play with count= or skip= for read and seek=
> for write to find a large enough contiguous area without bad blocks.

Konste,

may you please go to Device Drivers--->Memory Technology Device (MTD)
support--->UBI - Unsorted block images---> in menuconfig and enable "UBI
debugging", "UBI debugging messages", and "Extra self-checks" and try
again? Then send what UBI prints. I'll try to figure out what is wrong.

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

  parent reply	other threads:[~2007-09-06 11:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06  8:12 General performance of NAND operations i.e mount and ls Konstantin Kletschke
2007-09-06  8:27 ` Artem Bityutskiy
2007-09-06  8:44   ` Konstantin Kletschke
2007-09-06  9:11     ` Artem Bityutskiy
2007-09-06  9:37       ` Konstantin Kletschke
2007-09-06 10:53         ` Artem Bityutskiy
2007-09-06 11:21         ` Artem Bityutskiy
2007-09-06 11:11       ` Artem Bityutskiy [this message]
2007-09-06 16:03         ` Konstantin Kletschke
2007-09-07  5:47           ` Artem Bityutskiy
2007-09-07  7:44             ` Konstantin Kletschke
2012-06-25 12:01               ` JFFS2 CRC problems Stefan Roese

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=1189077119.14370.52.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lists@ku-gbr.de \
    /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