From: Rick Jones <rick.jones2@hp.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: BCM5704 performance questions.
Date: Fri, 10 Jun 2005 14:33:55 -0700 [thread overview]
Message-ID: <42AA0743.1020101@hp.com> (raw)
In-Reply-To: <42AA016C.9050801@candelatech.com>
> Have you done any tests with 2 tg3 NICs in a single machine to see if they
> can run at or near line speed (full duplex)?
It isn't just a question of two tg3 NICs in the same box is it? You are running
two NICs on the same bus right? And unless my dimm memory is mistaken, four
ports on a card with 5704s means two 5704's a bridge chip right? So, it would
be two tg3 NICs going through the same bridge chip, not just the same bus or
same system. I'd be worrying about DMA latencies on the system and the bridge
chip, and perhaps the efficiency of the PCI-X bus usage (not sure - is there
anything in your system's chipset to extract that sort of information?)
What happens when you turn pktgen around/insideout and source packets from the
bridging system to each of the (two other?) systems?
Since you are bridging, does having CKO enabled really matter? Mightn't that
allow the firmware on the 5704(s) to run a triffle faster? Or does bridging
already not request CKO (I suppose it might).
Are your interface interrupts distributed across the CPUs?
rick jones
next prev parent reply other threads:[~2005-06-10 21:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 0:38 BCM5704 performance questions Ben Greear
2005-06-09 23:56 ` Michael Chan
2005-06-10 1:24 ` Ben Greear
2005-06-10 0:37 ` Michael Chan
2005-06-10 21:09 ` Ben Greear
2005-06-10 21:16 ` Michael Chan
2005-06-10 22:35 ` Ben Greear
2005-06-10 22:43 ` David S. Miller
2005-06-10 21:33 ` Rick Jones [this message]
2005-06-10 21:56 ` Ben Greear
2005-06-10 22:03 ` Rick Jones
2005-06-10 22:25 ` Ben Greear
2005-06-10 14:03 ` Jason Lunz
2005-06-10 0:54 ` David S. Miller
2005-06-10 1:20 ` Ben Greear
2005-06-10 1:29 ` David S. Miller
2005-06-10 2:28 ` Ben Greear
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=42AA0743.1020101@hp.com \
--to=rick.jones2@hp.com \
--cc=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
/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).