From: Dan Malek <dan@embeddededge.com>
To: Ricardo Scop <scop@vanet.com.br>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linuxppc and MPC8255 routing performance
Date: Tue, 13 Nov 2001 12:02:37 -0500 [thread overview]
Message-ID: <3BF1522D.1010706@embeddededge.com> (raw)
In-Reply-To: 01111314034801.01064@scop.digitel.com.br
Ricardo Scop wrote:
> 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.
You don't need this as a solution to your performance troubles. I have
been experimenting with using this space for socket buffers, but unless
you have something else on the bus consuming the cycles, I haven't seen
any benefit. It could be very useful for custom network applications,
but there isn't anything Linux will do. Some systems just toss this space
into the general free memory pool, just remember you can't access it over
the 60x bus.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-13 17:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D73A25AA6E54D511AD74009027B1110F04F5E1@ORION>
2001-11-13 11:03 ` Linuxppc and MPC8255 routing performance Ricardo Scop
2001-11-13 17:02 ` Dan Malek [this message]
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=3BF1522D.1010706@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=scop@vanet.com.br \
/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;
as well as URLs for NNTP newsgroup(s).