From: "Harish Kulkarni" <hari@cosystech.com>
To: <netdev@oss.sgi.com>
Subject: Network Device-Driver/Layer Implementation: Help required
Date: Thu, 31 Oct 2002 13:25:18 +0530 [thread overview]
Message-ID: <NFBBKDONILLOCGDCFLLIAEALCGAA.hari@cosystech.com> (raw)
In-Reply-To: <15808.11521.25342.659187@robur.slu.se>
Hello all,
I have a T1/E1 device driver: ( completed till PCI initialization and other
device-internals initialization,including interrupts handling procedures),
now i am not understanding how to provide the interface to upper layers?. I
have walked through the lapb-module.txt and some code of IPX, but still the
things are not clear. Can any one help/guide me?
-Thanks
Hari
> -----Original Message-----
> From: netdev-bounce@oss.sgi.com [mailto:netdev-bounce@oss.sgi.com]On
> Behalf Of Robert Olsson
> Sent: Thursday, October 31, 2002 12:33 AM
> To: Cheng Jin
> Cc: jamal; netdev@oss.sgi.com
> Subject: Re: Linux SMP on 2.4.18-3
>
>
>
> Cheng Jin writes:
>
> > Out of curiosity, what is the maximum send rate (pps) under Linux
> > 2.4.18-3? I read in the paper that sending across two Intel
> Gbe with one
> > CPU gets up to 36o Kpps.
>
> Yes forwarding performance...
>
> A good chip/driver can itself do a lot more. I have seen very
> decent numbers
> with e1000, tg3 and dl2k. For FE tulip has been a top performer for long
> time but I also now see 144 kpps from my laptop w. 3c59x driver.
>
> Cheers.
> --ro
>
>
>
next prev parent reply other threads:[~2002-10-31 7:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 8:27 Linux SMP on 2.4.18-3 Cheng Jin
2002-10-28 12:47 ` jamal
2002-10-28 18:26 ` Cheng Jin
2002-10-30 19:03 ` Robert Olsson
2002-10-31 7:55 ` Harish Kulkarni [this message]
2002-10-31 16:35 ` Network Device-Driver/Layer Implementation: Help required James R. Leu
2002-11-04 13:10 ` Linux SMP on 2.4.18-3 jamal
2002-10-30 1:40 ` Boris Protopopov
2002-10-30 1:54 ` Jeff Garzik
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=NFBBKDONILLOCGDCFLLIAEALCGAA.hari@cosystech.com \
--to=hari@cosystech.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).