From: Steven Scholz <steven.scholz@imc-berlin.de>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: uncached user space mapping with mmap() ???
Date: Fri, 05 Mar 2004 09:18:27 +0100 [thread overview]
Message-ID: <404837D3.3060609@imc-berlin.de> (raw)
In-Reply-To: <40473464.8010203@imc-berlin.de>
Hi there,
thanks very much for all your help.
I used the stuff Stéphane suggested. But I have to ask again about
mapping of huge memory areas:
Let's say the peripheral has 32 MB address range staring at BASE. At
address GRAM 1MB of external SDRAM is located.
I use a simple test loop
p = (unsigned short *)
ioremap(base + GRAM, 32MB);
START ();
while (Retries--) {
for (i = 0; i < Size; i++) {
pData[i] = *p;
}
}
STOP ();
When I map only the the GRAM I get a throughput of
IoremapTest... 8.0 s => 2049.4 kW/s
But when I map the whole address range
p = (unsigned short *)
ioremap(BASE, imcdevif_iosize);
and move the pointer
p += GRAM;
before entering the test loop I only get
IoremapTest... 8.4 s => 1944.8 kW/s
How is that???
Is it always better to map only the small part I am going to use?
Thanks a million!
--
Steven Scholz
imc Measurement & Control imc Meßsysteme GmbH
Voltastr. 5 Voltastr. 5
13355 Berlin 13355 Berlin
Germany Deutschland
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-05 8:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 13:51 uncached user space mapping with mmap() ??? Steven Scholz
2004-03-04 17:00 ` Dan Malek
2004-03-05 8:18 ` Steven Scholz [this message]
2004-03-05 11:35 ` Jon Masters
2004-03-05 11:41 ` Steven Scholz
2004-03-05 13:21 ` Jon Masters
-- strict thread matches above, loose matches on Subject: below --
2004-03-04 14:15 Fillod Stephane
2004-03-04 14:35 ` Steven Scholz
2004-03-04 17:28 ` Eugene Surovegin
2004-03-04 14:47 Fillod Stephane
2004-03-04 14:51 ` Steven Scholz
2004-03-04 23:02 Richard Williams
2004-03-04 23:17 ` Dan Malek
2004-03-08 10:25 Fillod Stephane
2004-03-09 10:55 ` Jon Masters
2004-03-09 12:49 Fillod Stephane
2004-03-12 12:07 ` Jon Masters
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=404837D3.3060609@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.