From: Joseph Carter <knghtbrd@debian.org>
To: Troy Benjegerdes <hozer@drgw.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: natsemi.c (Netgear FA311 card) probmlems??
Date: Fri, 13 Apr 2001 05:38:09 -0700 [thread overview]
Message-ID: <20010413053809.E756@debian.org> (raw)
In-Reply-To: <B65FF72654C9F944A02CF9CC22034CE22E1B59@mail0.myrio.com> <3AC22661.E69BE205@mandrakesoft.com> <20010411213236.P13920@altus.drgw.net>
In-Reply-To: <20010411213236.P13920@altus.drgw.net>; from hozer@drgw.net on Wed, Apr 11, 2001 at 09:32:36PM -0500
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
On Wed, Apr 11, 2001 at 09:32:36PM -0500, Troy Benjegerdes wrote:
> > There are some improvements in the latest 2.4 test patch, 2.4.3-pre8. I
> > would be very interested in hearing feedback on that. I finally got two
> > test cards, FA311 and FA312, so I can work on it a bit too.
>
> Okay, I finally got around to testing this on 2.4.4-pre1. for the 5 or so
> minutes I've been using it so far, it seems okay (I'm able to log in this
> time), and I'm running NetPIPE to check performance.
>
> Perfomance isn't great (the peak bandwidth is 65 Mbps or so), but this
> could be partially due to my switch or the other machine I'm testing it
> with.
No, performance really is peaked about 65 Mbps or so at the moment. I'm
currently using the FA312 here, which was massively broken with my FA312
until 2.4.2-ac which updated the natsemi driver. I have a '311 in a P200
which worked fine before. This is an AMD box, but I suspect the problem
was the '312, not the AMD.
--
Joseph Carter <knghtbrd@debian.org> Free software developer
"This is the element_data structure for elements whose *element_type =
FORM_TYPE_SELECT_ONE, FORM_TYPE_SELECT_MULT. */ /* * nesting deeper
and deeper, harder and harder, go, go, oh, OH, OHHHHH!! * Sorry, got
carried away there. */ struct lo_FormElementOptionData_struct."
-- Mozilla source code
[-- Attachment #2: Type: application/pgp-signature, Size: 273 bytes --]
prev parent reply other threads:[~2001-04-13 12:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B65FF72654C9F944A02CF9CC22034CE22E1B59@mail0.myrio.com>
[not found] ` <3AC22661.E69BE205@mandrakesoft.com>
2001-04-12 2:32 ` natsemi.c (Netgear FA311 card) probmlems?? Troy Benjegerdes
2001-04-13 4:42 ` natsemi.c still broken Troy Benjegerdes
2001-04-13 12:38 ` Joseph Carter [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=20010413053809.E756@debian.org \
--to=knghtbrd@debian.org \
--cc=hozer@drgw.net \
--cc=linux-kernel@vger.kernel.org \
/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