From: Dan Malek <dan@embeddededge.com>
To: Ricardo Scop <scop@digitel.com.br>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linuxppc and MPC8255 routing performance
Date: Thu, 08 Nov 2001 16:45:15 -0500 [thread overview]
Message-ID: <3BEAFCEB.3090604@embeddededge.com> (raw)
In-Reply-To: 01110818021400.00999@scop.digitel.com.br
Ricardo Scop wrote:
> Even without secondary (L2) cache?
Yes. Depending upon the application, using the "backside" memory
for exclusive CPM use could be helpful.
> Err.. any suggestions, on those?
netperf comes to mind.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-08 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2001-11-09 9:55 ` Ricardo Scop
2001-11-09 16:34 ` Dan Malek
2001-11-09 18:08 ` Jerry Van Baren
[not found] <D73A25AA6E54D511AD74009027B1110F04F5E1@ORION>
2001-11-13 11:03 ` Ricardo Scop
2001-11-13 17:02 ` Dan Malek
2001-11-13 12:38 ` Ricardo Scop
2001-11-13 18:21 ` Dan Malek
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=3BEAFCEB.3090604@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=scop@digitel.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).