From: Arnaud Mouiche <arnaud.mouiche@thomson.net>
To: linux-mtd@lists.infradead.org
Subject: Re: flash read performance
Date: Thu, 30 Oct 2008 09:33:58 +0100 [thread overview]
Message-ID: <49097176.5010506@thomson.net> (raw)
In-Reply-To: <gea0sh$j97$1@ger.gmane.org>
Hi,
I was faced with the same wondering in the past : bootloader NOR access
was really much faster that Linux one.
Yes, no DMA was used (but the same on bootloader, and anyway that
doesn't impact the data rate, only the CPU load), but even worse, Linux
code was using memcpy_fromio which a basic byte by byte loop copy in the
default ARM implementation.
May be your issues are the same...
Regards,
arnaud
Andre Puschmann a écrit :
> Josh Boyer schrieb:
>
>>> In my opinion the read
>>> performance is very poor, only around 1.2 to 1.4 MB/s depending on the
>>> blocksize. I think it should be possible to get much higher transfer rates.
>>>
>> Why do you think that?
>>
>
> I guess there is something wrong with the timing parameters and/or the
> way the CPU core speaks to the flash controller, which results in long
> wait-states.
> But at least for my understanding, these transfer rates have nothign to
> do with _high speed NOR flashes_ :-)
>
>
>
>> Why do you think that? The chip drivers don't do DMA, so all I/O goes
>> through the CPU.
>>
>
> Yes, DMA is not used. However, the CPU should be strong enough to do
> this transfer faster. On the other hand, my understanding is, DMA brings
> no speed improvements in all cases. It boosts memory transfers without
> adding an extra overhead to the CPU. But in this case, copy data is the
> only task.
>
>
> Regards,
> Andre
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
next prev parent reply other threads:[~2008-10-30 8:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 10:14 flash read performance Andre Puschmann
2008-10-29 11:42 ` Josh Boyer
2008-10-29 12:03 ` Jamie Lokier
2008-10-29 15:52 ` Andre Puschmann
2008-10-30 8:33 ` Arnaud Mouiche [this message]
2008-10-30 9:52 ` Andre Puschmann
2008-10-30 10:06 ` Arnaud Mouiche
2008-11-03 14:23 ` Andre Puschmann
2008-11-04 8:30 ` Andre Puschmann
2008-11-04 11:42 ` Jamie Lokier
2008-11-04 14:31 ` Andre Puschman
2008-11-07 2:41 ` Trent Piepho
2008-11-07 4:02 ` Jamie Lokier
2008-11-07 5:36 ` Trent Piepho
2008-11-07 5:57 ` Jamie Lokier
2008-11-07 9:47 ` Andre Puschmann
2008-11-08 5:28 ` Trent Piepho
2008-11-11 13:28 ` Andre Puschmann
2008-11-15 2:02 ` Trent Piepho
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=49097176.5010506@thomson.net \
--to=arnaud.mouiche@thomson.net \
--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