9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com jmk@plan9.bell-labs.com
Subject: [9fans] ne2000
Date: Tue, 22 Jul 1997 16:29:59 -0400	[thread overview]
Message-ID: <19970722202959.SuGUtaUULt6XggxRICSBqp53YelvZvvlbMWyUHfafNc@z> (raw)

i can get 100% of a 100Mb/s link with UDP on a 21140 based card.
what are you doing wrong?

------ forwarded message follows ------

>From cse.psu.edu!owner-9fans Tue Jul 22 15:58:04 EDT 1997
Received: from cse.psu.edu ([130.203.3.50]) by plan9; Tue Jul 22 15:58:04 EDT 1997
Received: from localhost (majordom@localhost) by cse.psu.edu (8.8.6/8.7.3) with SMTP id PAA15035; Tue, 22 Jul 1997 15:37:03 -0400 (EDT)
Received: by claven.cse.psu.edu (bulk_mailer v1.5); Tue, 22 Jul 1997 15:36:57 -0400
Received: (from majordom@localhost) by cse.psu.edu (8.8.6/8.7.3) id PAA14996 for 9fans-outgoing; Tue, 22 Jul 1997 15:36:52 -0400 (EDT)
X-Authentication-Warning: claven.cse.psu.edu: majordom set sender to owner-9fans using -f
Received: from ncube.com (hundl.ncube.com [134.242.5.163]) by cse.psu.edu (8.8.6/8.7.3) with SMTP id PAA14989 for <9fans@cse.psu.edu>; Tue, 22 Jul 1997 15:36:46 -0400 (EDT)
From: ncube.com!beto
Message-Id: <199707221936.PAA14989@cse.psu.edu>
Date: Tue, 22 Jul 97 12:27:37 PDT
To: cse.psu.edu!9fans
Subject: Re: [9fans] ne2000
Sender: cse.psu.edu!owner-9fans
Reply-To: cse.psu.edu!9fans
Precedence: bulk

In <199707230448.64603.out.baker@plan9.cs.su.oz.au>
 David Hogan <dhog@lore.plan9.cs.su.oz.au> wrote:

> > the datsheets and application notes for the dp8390 explain most of what you need
> > to know about the wrteched ne2000. they're available on-line at the national
> > semiconductor website.
>
> Thanks, I'll check it out.
>
> > no matter how cheap you say it is, it's not worth the money.
>
> After looking at the driver code, I have to agree.  Reading in
> packets using INSx -- what is this, the stone age??
>
> The target application is talking to an ISDN gateway, so
> efficiency isn't crucial.  But if cable modem ever arrives,
> I'll probably want a better ethernet card (or if I get
> a second computer...).
>
> So, which ethernet cards do PCI bus mastering?  :-)

PCI Cogent Ethernet and Fast Ethernet adapters are very good.
We get 60% of a 100mbits link using UDP. These are not
supported on the release, but you could get the information to
write a driver from Digital Semiconductor
(DECchip 21140A PCI Fast ethenet Lan Controller).
The interface is very similar to a lance controller
and it does scatther send (up to two).












             reply	other threads:[~1997-07-22 20:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-07-22 20:29 jmk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-31  3:33 [9fans] NE2000 Vladimir
1997-07-23  3:11 [9fans] ne2000 jmk
1997-07-22 22:27 beto
1997-07-22 22:18 jmk
1997-07-22 21:47 beto
1997-07-22 21:10 beto
1997-07-22 20:50 Paul
1997-07-22 20:26 Mike
1997-07-22 19:32 jmk
1997-07-22 19:27 beto
1997-07-22 18:48 David
1997-07-22 13:22 jmk
1997-07-22  7:11 David

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=19970722202959.SuGUtaUULt6XggxRICSBqp53YelvZvvlbMWyUHfafNc@z \
    --to=jmk@plan9.bell-labs.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).