From: Ben Greear <greearb@candelatech.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com, mchan@broadcom.com
Subject: Re: BCM5704 performance questions.
Date: Thu, 09 Jun 2005 19:28:47 -0700 [thread overview]
Message-ID: <42A8FADF.90309@candelatech.com> (raw)
In-Reply-To: <20050609.182943.29573731.davem@davemloft.net>
David S. Miller wrote:
> From: Ben Greear <greearb@candelatech.com>
> Date: Thu, 09 Jun 2005 18:20:33 -0700
>
>
>>I ran a test using pktgen to (try to) send 82kpps, 1514 byte packets between
>>two ports on the tg3 NIC. It can do about 780Mbps in one direction,
>>and 880Mbps in the other direction. Lots of harmless hard-start xmit errors reported
>>(tg3 may not stop it's tx queue correctly, or maybe pktgen is screwed up since
>>e1000 reports similar errors).
>
>
> There is a known race on SMP with drivers using NETIF_F_LLTX that is
> still not fixed. It will cause the error message to be reported from
> the driver's ->hard_start_xmit() routine when you hit this race.
Ok, it's not a big deal, since I can just retry the packet when
the tx queue wakes up again. The message was coming from pktgen, btw.
> You're definitely on an SMP system if you are triggering that message.
Yes, dual xeon with HT as well.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2005-06-10 2:28 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
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 [this message]
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=42A8FADF.90309@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@davemloft.net \
--cc=mchan@broadcom.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).