From: beto@ncube.com beto@ncube.com
Subject: [9fans] ne2000
Date: Tue, 22 Jul 1997 15:27:25 -0700 [thread overview]
Message-ID: <19970722222725.zh_f-Vyh1d9AIto8n9jD96eaZQ0tVV-2Nhypi7-dQZQ@z> (raw)
In <199707222220.SAA00887@cse.psu.edu>
jmk@plan9.bell-labs.com wrote:
> From: ncube.com!beto
>
> In <199707222030.QAA16117@cse.psu.edu>
> jmk@plan9.bell-labs.com wrote:
>
> > i can get 100% of a 100Mb/s link with UDP on a 21140 based card.
> > what are you doing wrong?
> >
> Is this brazil or plan9?
>
> brazil. using ttcp -u. all the bytes get to the other end.
>
What about TCP performance?
We are only getting 35mbits using ttcp.
next reply other threads:[~1997-07-22 22:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-22 22:27 beto [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:18 jmk
1997-07-22 21:47 beto
1997-07-22 21:10 beto
1997-07-22 20:50 Paul
1997-07-22 20:29 jmk
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=19970722222725.zh_f-Vyh1d9AIto8n9jD96eaZQ0tVV-2Nhypi7-dQZQ@z \
--to=beto@ncube.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).