public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Jonas Holmberg <jonas.holmberg@axis.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: ????????? <lnys@avamax.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: nand flash driver problem
Date: Tue, 13 Jan 2004 14:08:01 +0100	[thread overview]
Message-ID: <20040113130800.GB29496@axis.com> (raw)
In-Reply-To: <1073976604.5541.10.camel@imladris.demon.co.uk>

On Tue, Jan 13, 2004 at 06:50:05AM +0000, David Woodhouse wrote:
> On Tue, 2004-01-13 at 11:30 +0800, ????????? wrote:
> >              I also do another test for reading or writing Nand flash by MTD
> > block driver and it is ok (I mean reading or writing 200KB data from/to Nand
> > flash is not more than 1 second).  So I don't know what the problem is. Do
> > anyone meet the similar problem or any idea?
> 
> Use profiling to see where it's spending all its time. Read the
> 'readprofile' man page.

The time it takes to write to a regular file depends a lot on the 
buffer size when copying data. Some implementations of cp, for 
example, always use the same buffer size and doesn't use stat or 
statfs to find out the blocksize of the destination file system. I 
guess the compression in JFFS2 is a bottleneck when copying too small 
chunks.

/Jonas

  reply	other threads:[~2004-01-13 13:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13  3:30 nand flash driver problem 林意翔
2004-01-13  6:50 ` David Woodhouse
2004-01-13 13:08   ` Jonas Holmberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-17 21:52 Nand " Olivier ERIBON
2002-05-18  7:11 ` David Woodhouse

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=20040113130800.GB29496@axis.com \
    --to=jonas.holmberg@axis.com \
    --cc=dwmw2@infradead.org \
    --cc=lnys@avamax.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