From: Ricardo Scop <scop@vanet.com.br>
To: Ken Applebaum <applebaumk@embeddedplanet.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linuxppc and MPC8255 routing performance
Date: Tue, 13 Nov 2001 14:03:48 +0300 [thread overview]
Message-ID: <01111314034801.01064@scop.digitel.com.br> (raw)
In-Reply-To: <D73A25AA6E54D511AD74009027B1110F04F5E1@ORION>
Hi, Ken
On Monday 12 November 2001 18:28, Ken Applebaum wrote:
> ricardo,
>
> does your board have both banks of memory populated?
>
If you mean 'both banks" as a memory bank at the local bus and another at the
60x bus, the answer is yes, our prototype hardware has them, for hardware
debugging purposes. But I didn't enable the use of the local memory bank in
Linux so far, because we didn't originally intend to use it in our final
product...
Nevertheless, I'm aware that using local bus memory for I/O data flowing
between CPM and CPU may improve performance in some Linux applications, so I
would like to experiment with this. Unfortunatelly, I'm very new to Linux, so
I don't know how to configure it for using local memory. If you have any
ideas...
Thanks.
~Ricardo
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2001-11-13 11:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D73A25AA6E54D511AD74009027B1110F04F5E1@ORION>
2001-11-13 11:03 ` Ricardo Scop [this message]
2001-11-13 17:02 ` Linuxppc and MPC8255 routing performance Dan Malek
2001-11-13 12:38 ` Ricardo Scop
2001-11-13 18:21 ` Dan Malek
2001-11-13 21:09 ` Re[2]: " Ricardo Scop
2001-11-20 17:07 ` eth1 FEC on RPX-CLLF info sruel
2001-11-20 19:03 ` Wolfgang Denk
2001-11-07 20:30 Linuxppc and MPC8255 routing performance Ricardo Scop
2001-11-08 19:41 ` Dan Malek
2001-11-08 15:02 ` Ricardo Scop
2001-11-08 20:43 ` Val Henson
2001-11-08 21:45 ` Dan Malek
2001-11-09 9:55 ` Ricardo Scop
2001-11-09 16:34 ` Dan Malek
2001-11-09 18:08 ` Jerry Van Baren
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=01111314034801.01064@scop.digitel.com.br \
--to=scop@vanet.com.br \
--cc=applebaumk@embeddedplanet.com \
--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.