All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: 8169 driver with NetGear GA511 card.
Date: Thu, 28 Oct 2004 10:47:48 -0700	[thread overview]
Message-ID: <418130C4.3010207@candelatech.com> (raw)
In-Reply-To: <20041028074827.GA3572@electric-eye.fr.zoreil.com>

Francois Romieu wrote:

> The r8169 in -mm and in -netdev includes some extra buzzword-compliant
> features (TX csum/SG and TSO mainly). The changes are isolated in a
> single patch against 2.6.9 available at:
> http://www.fr.zoreil.com/people/francois/misc/20041020-2.6.9-r8169.c-test.patch
> 
> I will not claim it is as stable as vanilla 2.6.9 should be.

I'm running tests at the ethernet frame (skb) level, so I would not
expect the IP offload to help much.

Do you have any performance numbers for your 8169 cards for me to
compare against?

> Please send the usuals 'lspci -vx' + /proc/interrupts contents during
> activity + complete dmesg + short description of the generated traffic.
> I will hardly dissect it before the week end but there is a problem. :o(

I'll get this in a bit, as I have locked up the keyboard again.  This time,
I was still using the non-NAPI code which had run over-night at around 5Mbps...

I tried a different network setup, and noticed that the 8169 was only
negotiating 10bt/HD.  That would explain the poor performance numbers.
The NIC was connected to a BCM5705M when I noticed this, though it had
been connected to an e1000 earlier.

I tried forcing both NICs to 100bt/FD.  The BCM would force to that speed,
but the 8169 would only force to 100bt/HD.  While attempting to change them
back to auto-negotiate, I noticed that the keyboard had quit working...

With regard to the BCM, it is interesting in that ethtool reports that it
supports only up to 100bt/FD, but it advertises 1000bt/FD.

The wierd advertise and negotiation stuff could be at least partly my
fault as I have a program that manipulates these settings from default.
I will continue to play with this later this evening...

Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2004-10-28 17:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27 23:18 8169 driver with NetGear GA511 card Ben Greear
2004-10-28  1:58 ` Ben Greear
2004-10-28  7:48 ` Francois Romieu
2004-10-28 17:47   ` Ben Greear [this message]
2004-10-28 22:37     ` Francois Romieu
2004-10-28 22:49       ` Ben Greear
2004-10-28 22:00   ` [PATCH] r8169 tx checksuming on by default Jon Mason
2004-10-28 16:45 ` 8169 driver with NetGear GA511 card Jon Mason
2004-10-28 16:52   ` 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=418130C4.3010207@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=netdev@oss.sgi.com \
    --cc=romieu@fr.zoreil.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 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.