From: Ben Greear <greearb@candelatech.com>
To: Ramesh Chaurasiya <rchaurasiya@cse.iitk.ac.in>
Cc: netdev@oss.sgi.com
Subject: Re: buffer overruns
Date: Sat, 24 Apr 2004 00:55:31 -0700 [thread overview]
Message-ID: <408A1D73.5030705@candelatech.com> (raw)
In-Reply-To: <Pine.GSO.4.10.10404241055580.17512-100000@cseultra3.cse.iitk.ac.in>
Ramesh Chaurasiya wrote:
> Hi,
> Whenever I try to receive traffic at more than 500 Mbps, many packets
> are being dropped as shown in ifconfig. There are many overruns and errors
> in Rx packets details of ifconfig. I am using Intel PRO 1000 Gigabit NIC,
> linux 2.4.20-8smp and dual processsor Xeon Machine with a 32bit/33 MHz PCI
> bus. What does this error means. Am I dropping packets at
> NIC/driver/kernel buffers/application socket? What new hardware should I
> use to overcome this. I am using latest e1000 drivers compiled with NAPI
> support. Please help me out.
> Thanks,
> Ramesh.
Get a 64-bit PCI-X bus, and set the RxDescriptors and TxDescriptors
in the e1000 driver to 4096.
With that, I can get about 999Mbps rx + tx on two ports.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2004-04-24 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-24 5:30 buffer overruns Ramesh Chaurasiya
2004-04-24 7:55 ` Ben Greear [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=408A1D73.5030705@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
--cc=rchaurasiya@cse.iitk.ac.in \
/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).