From: "Jeremy M. Guthrie" <jeremy.guthrie@berbee.com>
To: netdev@oss.sgi.com
Cc: Robert Olsson <Robert.Olsson@data.slu.se>,
Stephen Hemminger <shemminger@osdl.org>,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: V2.4 policy router operates faster/better than V2.6
Date: Wed, 12 Jan 2005 10:24:59 -0600 [thread overview]
Message-ID: <200501121025.03899.jeremy.guthrie@berbee.com> (raw)
In-Reply-To: <16869.15931.324875.264756@robur.slu.se>
[-- Attachment #1: Type: text/plain, Size: 4775 bytes --]
On Wednesday 12 January 2005 09:11 am, Robert Olsson wrote:
> Jeremy M. Guthrie writes:
> > > Did the e1000 patch cure the problem that interrupts got enabled for
> > > unidirectional traffic? Ring size? I've never seen any win in system
> > > performance w. RX rings larger than 256 at least not in lab.
> >
> > ETH3 Interrupts(calc'd from below): 1479968
> > ETH2 Interrupts: 261543
> > Packets RX'd on ETH3: 3892720
> > Packets dropped on RX on ETH3: 10305
>
> Very strange...
>
> eth3 is bound to CPU0 which in turn has all packet load... If we were
> to believe your CPU0 was saturated (due to the drops). We should see no
> (RX) interrupts on eth3. But there is a lot... one irq per every three
> packet. Why?
I have no idea why it would be doing this.
> Can you investigate? e1000 has problem like this w. unidirectional traffic
> w/o the patch I sent.
This appears to be where this problem is getting beyond my expertise. I
verified NAPI is turned on. I also verified the patch is in place. I am
open to suggestions but otherwise I am not the worlds best coder.
> Or is your traffic so extremely bursty. No?
By the nature of our business it can be very bursty. We just have so many
sources/destinations for traffic that our traffic is generally pretty bursty.
We might be running 300-400 mbps with spikes of 40-100 mbps.
> --ro
>
> > This equates to about a 0.26% drop rate. W/ 256 packet RX ring size I
> > see about a 0.42% drop rate.
> >
> > This is using both the newest Intel driver w/ your patch and an
> > increased ring size of 2048.
> >
> > Tue Jan 11 19:15:04 CST 2005
> > eth3 Link encap:Ethernet HWaddr 00:02:B3:D5:7E:30
> > inet addr:10.253.0.1 Bcast:10.255.255.255 Mask:255.255.255.0
> > inet6 addr: fe80::202:b3ff:fed5:7e30/64 Scope:Link
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:2337377824 errors:14992144 dropped:14992144
> > overruns:9643826 frame:0
> > TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:3984064976 (3799.5 Mb) TX bytes:398 (398.0 b)
> > Base address:0x22a0 Memory:eff80000-effa0000
> >
> > CPU0 CPU1
> > 0: 93627934 353254270 IO-APIC-edge timer
> > 1: 35 507 IO-APIC-edge i8042
> > 7: 0 0 IO-APIC-level ohci_hcd
> > 8: 0 2 IO-APIC-edge rtc
> > 12: 73 145 IO-APIC-edge i8042
> > 14: 120 313 IO-APIC-edge ide0
> > 18: 2158179576 1815 IO-APIC-level eth3
> > 20: 2 2136514988 IO-APIC-level eth2
> > 27: 204201 371301 IO-APIC-level eth0
> > 28: 14585 75320 IO-APIC-level aic7xxx
> > 30: 0 0 IO-APIC-level acpi
> > NMI: 0 0
> > LOC: 446922783 446921227
> > ERR: 0
> > MIS: 0
> >
> > Tue Jan 11 19:16:05 CST 2005
> > eth3 Link encap:Ethernet HWaddr 00:02:B3:D5:7E:30
> > inet addr:10.253.0.1 Bcast:10.255.255.255 Mask:255.255.255.0
> > inet6 addr: fe80::202:b3ff:fed5:7e30/64 Scope:Link
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:2341270544 errors:15002449 dropped:15002449
> > overruns:9652393 frame:0
> > TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:1664751812 (1587.6 Mb) TX bytes:398 (398.0 b)
> > Base address:0x22a0 Memory:eff80000-effa0000
> >
> > CPU0 CPU1
> > 0: 93639955 353302319 IO-APIC-edge timer
> > 1: 35 507 IO-APIC-edge i8042
> > 7: 0 0 IO-APIC-level ohci_hcd
> > 8: 0 2 IO-APIC-edge rtc
> > 12: 73 145 IO-APIC-edge i8042
> > 14: 120 313 IO-APIC-edge ide0
> > 18: 2159659544 1815 IO-APIC-level eth3
> > 20: 2 2136776531 IO-APIC-level eth2
> > 27: 204245 371369 IO-APIC-level eth0
> > 28: 14593 75343 IO-APIC-level aic7xxx
> > 30: 0 0 IO-APIC-level acpi
> > NMI: 0 0
> > LOC: 446982858 446981302
> > ERR: 0
> > MIS: 0
--
--------------------------------------------------
Jeremy M. Guthrie jeremy.guthrie@berbee.com
Senior Network Engineer Phone: 608-298-1061
Berbee Fax: 608-288-3007
5520 Research Park Drive NOC: 608-298-1102
Madison, WI 53711
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-12 16:24 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 20:55 V2.4 policy router operates faster/better than V2.6 Jeremy M. Guthrie
2005-01-03 22:51 ` Stephen Hemminger
2005-01-03 22:56 ` Jeremy M. Guthrie
2005-01-05 13:18 ` Robert Olsson
2005-01-05 15:18 ` Jeremy M. Guthrie
2005-01-05 16:30 ` Robert Olsson
2005-01-05 17:35 ` Jeremy M. Guthrie
2005-01-05 19:25 ` Jeremy M. Guthrie
2005-01-05 20:22 ` Robert Olsson
2005-01-05 20:52 ` Jeremy M. Guthrie
2005-01-06 15:26 ` Jeremy M. Guthrie
2005-01-06 18:15 ` Robert Olsson
2005-01-06 19:35 ` Jeremy M. Guthrie
2005-01-06 20:29 ` Robert Olsson
2005-01-06 20:54 ` Jeremy M. Guthrie
2005-01-06 20:55 ` Jeremy M. Guthrie
2005-01-06 21:19 ` Jeremy M. Guthrie
2005-01-06 21:36 ` Robert Olsson
2005-01-06 21:46 ` Jeremy M. Guthrie
2005-01-06 22:11 ` Robert Olsson
2005-01-06 22:18 ` Jeremy M. Guthrie
2005-01-06 22:35 ` Robert Olsson
2005-01-07 16:17 ` Jeremy M. Guthrie
2005-01-07 19:18 ` Robert Olsson
2005-01-07 19:38 ` Jeremy M. Guthrie
2005-01-07 20:07 ` Robert Olsson
2005-01-07 20:14 ` Jeremy M. Guthrie
2005-01-07 20:40 ` Robert Olsson
2005-01-07 21:06 ` Jeremy M. Guthrie
2005-01-07 21:30 ` Robert Olsson
2005-01-11 15:11 ` Jeremy M. Guthrie
2005-01-07 22:28 ` Jesse Brandeburg
2005-01-07 22:50 ` Jeremy M. Guthrie
2005-01-07 22:57 ` Stephen Hemminger
2005-01-11 15:17 ` Jeremy M. Guthrie
2005-01-11 16:40 ` Robert Olsson
2005-01-12 1:27 ` Jeremy M. Guthrie
2005-01-12 15:11 ` Robert Olsson
2005-01-12 16:24 ` Jeremy M. Guthrie [this message]
2005-01-12 19:27 ` Robert Olsson
2005-01-12 20:11 ` Jeremy M. Guthrie
2005-01-12 20:21 ` Robert Olsson
2005-01-12 20:30 ` Jeremy M. Guthrie
2005-01-12 20:45 ` Jeremy M. Guthrie
2005-01-12 22:02 ` Robert Olsson
2005-01-12 22:21 ` Jeremy M. Guthrie
[not found] ` <16869.42247.126428.508479@robur.slu.se>
2005-01-12 22:42 ` Jeremy M. Guthrie
2005-01-12 22:47 ` Jeremy M. Guthrie
2005-01-12 23:19 ` Robert Olsson
2005-01-12 23:23 ` Jeremy M. Guthrie
2005-01-13 8:56 ` Robert Olsson
2005-01-13 19:28 ` Jeremy M. Guthrie
2005-01-13 20:00 ` David S. Miller
2005-01-13 20:43 ` Jeremy M. Guthrie
2005-01-13 23:13 ` David S. Miller
2005-01-13 21:12 ` Robert Olsson
2005-01-13 22:27 ` Jeremy M. Guthrie
2005-01-14 15:44 ` Robert Olsson
2005-01-14 14:59 ` Jeremy M. Guthrie
2005-01-14 16:05 ` Robert Olsson
2005-01-14 19:00 ` Jeremy M. Guthrie
2005-01-14 19:26 ` Jeremy M. Guthrie
2005-01-16 12:32 ` Robert Olsson
2005-01-16 16:22 ` Jeremy M. Guthrie
2005-01-19 15:03 ` Jeremy M. Guthrie
2005-01-19 22:18 ` Robert Olsson
2005-01-20 1:50 ` Jeremy M. Guthrie
2005-01-20 11:30 ` Robert Olsson
2005-01-20 14:37 ` Jeremy M. Guthrie
2005-01-20 17:01 ` Robert Olsson
2005-01-20 17:14 ` Jeremy M. Guthrie
2005-01-20 21:53 ` Robert Olsson
2005-01-21 21:20 ` Jeremy M. Guthrie
2005-01-21 15:23 ` Robert Olsson
2005-01-21 21:24 ` Jeremy M. Guthrie
2005-01-31 15:37 ` Jeremy M. Guthrie
2005-01-31 18:06 ` Robert Olsson
2005-01-12 22:05 ` Jeremy M. Guthrie
2005-01-12 22:22 ` Robert Olsson
2005-01-12 22:30 ` Jeremy M. Guthrie
2005-01-11 17:17 ` Jeremy M. Guthrie
2005-01-11 18:46 ` Robert Olsson
2005-01-12 1:30 ` Jeremy M. Guthrie
2005-01-12 16:02 ` Robert Olsson
2005-01-04 15:07 ` Jeremy M. Guthrie
[not found] <200501071619.54566.jeremy.guthrie@berbee.com>
2005-01-07 23:23 ` Jesse Brandeburg
2005-01-10 21:11 ` Jeremy M. Guthrie
[not found] <C925F8B43D79CC49ACD0601FB68FF50C02D39006@orsmsx408>
2005-01-13 22:55 ` Jeremy M. Guthrie
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=200501121025.03899.jeremy.guthrie@berbee.com \
--to=jeremy.guthrie@berbee.com \
--cc=Robert.Olsson@data.slu.se \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).