From: Ben Greear <greearb@candelatech.com>
To: satya srikanth <satyasrikanth2001@yahoo.com>
Cc: Cheng Jin <chengjin@cs.caltech.edu>,
"Xiaoliang (David) Wei" <weixl@caltech.edu>,
"netdev@oss.sgi.com" <netdev@oss.sgi.com>
Subject: Re: gigabit ethernet
Date: Sun, 15 Feb 2004 20:32:09 -0800 [thread overview]
Message-ID: <403047C9.8020908@candelatech.com> (raw)
In-Reply-To: <20040214140914.3341.qmail@web21107.mail.yahoo.com>
satya srikanth wrote:
> My CPU is unable to handle anything more than this. Is
> it possible to handle 1000Mbps for any packet size or
> atleast something better than this by using more
> powerful machines. If anyone of you have experimented
> with this, can you give an idea of what kind of a
> machine do I need for this.
Try a machine with a 64/66 PCI bus, or preferably,
a PCI-X bus that can run 64/100 or better.
I got line speed packet generation and reception on
a dual 2.8Ghz Xeon machine with PCI-X (64/100) bus and a dual
port Intel pro/1000 NIC. I tested with 1500 byte packets
and transmitted and received 999Mbps of traffic between
two ports (total of ~4Gbps across the PCI backplane).
I wasn't routing or anything like that, but at least for
packet generation it worked fine.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2004-02-16 4:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 8:39 gigabit ethernet satya srikanth
2004-02-12 9:34 ` Xiaoliang (David) Wei
2004-02-13 10:38 ` satya srikanth
2004-02-13 19:36 ` Cheng Jin
2004-02-13 21:31 ` Nivedita Singhvi
2004-02-13 22:11 ` Jeff Garzik
2004-02-14 14:09 ` satya srikanth
2004-02-16 4:32 ` Ben Greear [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-22 16:56 Gigabit Ethernet Gilad Rom
2005-03-22 21:04 ` Dan Malek
2005-04-06 11:01 ` Bogdan Vacaliuc
2005-04-06 11:01 ` Bogdan Vacaliuc
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=403047C9.8020908@candelatech.com \
--to=greearb@candelatech.com \
--cc=chengjin@cs.caltech.edu \
--cc=netdev@oss.sgi.com \
--cc=satyasrikanth2001@yahoo.com \
--cc=weixl@caltech.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.