public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lisong Xu" <lxu2@unity.ncsu.edu>
To: <linux-kernel@vger.kernel.org>
Subject: Fw: Intel PRO/1000 NIC
Date: Fri, 19 Sep 2003 16:30:10 -0400	[thread overview]
Message-ID: <00fe01c37eec$d28be130$8c330e98@nanegrc> (raw)

Hello,

Just in case you have a similar problem.

The possible reason is that the on-board Inter 1000 chip of Dell PowerEdge
1600SC is Intel 82540EM, which is running PCI 32/33 or PCI 32/66.

Lisong

----- Original Message ----- 
From: Lisong Xu
To: netdev@oss.sgi.com ; linux-kernel@vger.kernel.org
Sent: Monday, September 15, 2003 10:35 AM
Subject: Intel PRO/1000 NIC


Hello,

I am sending UDP data from one PC to another PC directly through a cross
cable. The NIC of sender is Intel® PRO/1000 MT Server Adapter, and the NIC
of receiver is on-board Intel PRO/1000 (Dell PowerEdge 1600SC).

After tuning the kernel and driver parameters, the sender can send data at
1Gbps. But the receiver can only receive data at 620Mbps. (see the following
ifconfig messages, 30 seconds test)

*********** Sender *******************
eth1      Link encap:Ethernet  HWaddr 00:07:E9:17:84:36
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
          RX packets:111 errors:0 dropped:0 overruns:0 frame:0
          TX packets:418072 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:30000
          RX bytes:26193 (25.5 Kb)  TX bytes:3759596626 (3585.4 Mb)
          Interrupt:24 Base address:0xccc0 Memory:fcd00000-fcd20000
**************Receiver***********************
eth0      Link encap:Ethernet  HWaddr 00:C0:9F:1E:3A:46
          inet addr:192.168.1.101  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
          RX packets:261355 errors:156688 dropped:156688 overruns:156688
frame:0   <---- Look here!!!!!
          TX packets:97 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:30000
          RX bytes:2350019728 (2241.1 Mb)  TX bytes:22821 (22.2 Kb)
          Interrupt:11 Base address:0xecc0 Memory:fe100000-fe120000
***************************************************

My questions is why so many packets are "errors, dropped, overruns". I have
adjusted the "TxDescriptors, RxDescriptors, RxIntDelay,
RxAbsIntDelay, TxIntDelay, TxAbsIntDelay" for different values, but always
got similar result.

Maybe here is not the right email list to send, but I am really frustrated
with this problems, and hope to get some suggestions from the experts
here.Any suggestion is really appreciated!

Lisong


                 reply	other threads:[~2003-09-19 20:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='00fe01c37eec$d28be130$8c330e98@nanegrc' \
    --to=lxu2@unity.ncsu.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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