netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Lunz <lunz@falooley.org>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: netdev@oss.sgi.com, becker@scyld.com, jgarzik@mandrakesoft.com,
	"Patrick R. McManus" <mcmanus@ducksong.com>
Subject: Re: [PATCH] 2.4.20-pre sundance.c cleanups
Date: Thu, 19 Sep 2002 00:14:03 -0400	[thread overview]
Message-ID: <20020919041403.GA10527@orr.falooley.org> (raw)
In-Reply-To: <200209190353.g8J3r5q28456@vindaloo.ras.ucalgary.ca>

On Wed, Sep 18, 2002 at  9:53PM -0600, Richard Gooch wrote:
> - the driver is reporting 10 Mbps rather than 100 Mbps. I've actually
>   measured eth0 and eth2 and these are delivering 100 Mbps

i've noticed this too, and it's probably from all the mucking about I
did trying to combine becker's method of forcing duplex/speed with the
one in 2.4.19. That stuff is unrelated to the other, more-important
merges I did that actually affect how well the card works. Jeff rightly
pointed out that I should separate out chunks of the patch for
submission, but I haven't had time.

This card is still nowhere near working well, even with my patch. It
silently drops many frames when simultaneously sending and receiving at
high packet rates. It also locks up under load, and is reset in
tx_timeout. This happens less frequently with my patch, but is not
entirely gone.

Also, I need to investigate yet another variation on this driver, as
pointed out in
http://www.ussg.iu.edu/hypermail/linux/kernel/0209.0/1107.html

Jason

  reply	other threads:[~2002-09-19  4:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-28 18:56 [PATCH] 2.4.20-pre sundance.c cleanups Jason Lunz
2002-08-28 23:13 ` Jason Lunz
2002-09-19  3:53   ` Richard Gooch
2002-09-19  4:14     ` Jason Lunz [this message]
2002-09-19  4:25       ` [PATCH] 2.4.20-pre sundance.c update Jeff Garzik
2002-09-19  4:56         ` Jason Lunz
2002-09-19  5:11           ` Jeff Garzik
2002-09-19 13:23         ` Donald Becker
2002-09-19 17:12           ` PATCH: sundance #2 Jeff Garzik
2002-09-19 17:29             ` Donald Becker
2002-09-19 18:13               ` Jeff Garzik
2002-09-19 18:18               ` PATCH: sundance #3 Jeff Garzik
2002-09-19 19:30           ` PATCH: sundance #4 Jeff Garzik
2002-09-19 20:51             ` PATCH: sundance #4a Jason Lunz
2002-09-19 21:09               ` Jeff Garzik
2002-09-19 20:52             ` PATCH: sundance #4b Jason Lunz
2002-09-19 21:14               ` Jeff Garzik
2002-09-19 21:03             ` PATCH: sundance #5 (variable per-interface MTU support) Jason Lunz
2002-09-19 21:19               ` Jeff Garzik
2002-09-19 22:28               ` Donald Becker
2002-09-19 21:35             ` PATCH: [my] sundance #5 Jeff Garzik
2002-09-20  0:18               ` PATCH: sundance #6 Jeff Garzik
2002-09-19  6:42       ` [PATCH] 2.4.20-pre sundance.c cleanups Richard Gooch
2002-09-19  7:11         ` Keith Owens
2002-09-19 12:58     ` Donald Becker

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=20020919041403.GA10527@orr.falooley.org \
    --to=lunz@falooley.org \
    --cc=becker@scyld.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=mcmanus@ducksong.com \
    --cc=netdev@oss.sgi.com \
    --cc=rgooch@ras.ucalgary.ca \
    /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).