| To: | Christine Siegel <siegel@xxxxxxx>, discussion@xxxxxxxxxx |
|---|---|
| Subject: | Re: [Discussion] "Slowest link" reported at 10G when it is 1G |
| From: | Richard Carlson <rcarlson@xxxxxxxxxxxxx> |
| Date: | Sat, 09 Dec 2006 10:33:52 -0500 |
|
Hi Christine; This is a byproduct of a Gigabit Ethernet adapter doing interrupt coalescing. The link detection system uses packet pair timings to determine the bottleneck link speed. Each packet is timestamped by the appropriate Libpcap function when the packet is processed by the kernel. With interrupt coalescing, the NIC holds onto the packets until several have arrived and then it generates a single interrupt to the kernel. This reduces the load on the CPU, but it means that the packets timestamps are measuring how fast the packets can be transferred across the systems' memory bus. Not the how fast they arrive at the interface. The simple workaround is to look at the documentation for your NIC in the kernel's Documentation/networking directory. Turning off the interrupt coalescing option will increase the CPU load, but the NDT server will correctly report the bottleneck link capacity. Hopefully I can develop a better solution in the near future. Regards; Rich At 04:42 PM 12/8/2006, Christine Siegel wrote: Now that we have our NDT server up and running, testing using a workstation with a 1G connection to the network is reported by NDT to have a "slowest link" of 10G (OC-192). Can you explain? ------------------------------------ Richard A. Carlson e-mail: RCarlson@xxxxxxxxxxxxx Network Engineer phone: (734) 352-7043 Internet2 fax: (734) 913-4255 1000 Oakbrook Dr; Suite 300 Ann Arbor, MI 48104
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Discussion] "Slowest link" reported at 10G when it is 1G, Christine Siegel |
|---|---|
| Previous by Thread: | [Discussion] "Slowest link" reported at 10G when it is 1G, Christine Siegel |
| Indexes: | [Date] [Thread] [Top] [All Lists] |