From: "Paweł Staszewski" <pstaszewski@itcare.pl>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Eric Dumazet <dada1@cosmosbay.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
Linux Network Development list <netdev@vger.kernel.org>
Subject: Re: weird problem
Date: Tue, 30 Jun 2009 10:36:27 +0200 [thread overview]
Message-ID: <4A49CE8B.7080402@itcare.pl> (raw)
In-Reply-To: <4A49CE44.6030001@itcare.pl>
[-- Attachment #1: Type: text/plain, Size: 2270 bytes --]
sorry i forgot to attach file
Paweł Staszewski pisze:
> Jarek Poplawski pisze:
>> On 26-06-2009 19:45, Pawe. Staszewski wrote:
>>
>>> Eric Dumazet pisze:
>>>
>> ...
>>
>>>> Pawel made some reports errors in fib thread, so I am not sure he
>>>> really
>>>> tried 2.6.30 and had same oprofile results.
>>>>
>>>> rt_worker_func() taking 13% of cpu0 is an alarm for me :)
>>>> And 21% of cpu0 and 34% of cpu6 taken by oprofiled seems odd too...
>>>>
>>>> Pawel, could you give us :
>>>>
>>>> grep . /proc/sys/net/ipv4/route/*
>>>> cat /proc/interrupts
>>>>
>>>> on your various kernels (previous to 2.6.29, 2.6.29, 2.6.30, ...)
>>>>
>>>> I suspect a change in hash table size, and/or change in interrupt
>>>> affinities...
>>>>
>>
>> Btw., Pawel these eth0's don't look like affined or I miss something?
>>
>> Jarek P.
>> ...
>>
>>> cat /proc/interrupts
>>> CPU0 CPU1 CPU2 CPU3 CPU4
>>> CPU5 CPU6 CPU7
>>>
>> ...
>>
>>> 29: 1139988 18351004 89662 3 0
>>> 1 0 3 PCI-MSI-edge eth0
>>> 30: 0 2 20221692 1 0
>>> 3 0 0 PCI-MSI-edge eth1
>>>
>> ...
>>
> Yes
> it don't look because i switch a little later after some seconds with
> traffic on this host
>
> Cpu1 - 18351004 interrupts on eth0 (and yes here i forgot to change on
> boot so there are some interrupts cpu0 1139988 / cpu2 89662)
> Cpu2 - 20221692 interrupts on eth1
>
>
> in attached file are new stats with more counters from /cat
> /proc/interrupts
>
>
>
>>> second machine:
>>> Linux TM_02_C1 2.6.30 #1 SMP Thu Jun 25 21:49:58 CEST 2009 i686
>>> Intel(R) Xeon(R) CPU 3075 @ 2.66GHz GenuineIntel GNU/Linux
>>>
>>> cat /proc/interrupts
>>> CPU0 CPU1
>>>
>> ...
>>
>>> 28: 13482 11260 PCI-MSI-edge eth2
>>> 29: 3 1326457765 PCI-MSI-edge eth1
>>> 30: 1240943198 137973134 PCI-MSI-edge eth0
>>>
>>
>>
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
[-- Attachment #2: interrupts_aff.txt --]
[-- Type: text/plain, Size: 3678 bytes --]
cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
0: 223 0 1 145 169 197 183 171 IO-APIC-edge timer
1: 0 0 0 1 0 0 0 1 IO-APIC-edge i8042
9: 0 0 0 0 0 0 0 0 IO-APIC-fasteoi acpi
14: 0 0 0 0 0 0 0 0 IO-APIC-edge ide0
15: 0 0 0 0 0 0 0 0 IO-APIC-edge ide1
29: 1139988 415979141 89662 3 0 1 0 3 PCI-MSI-edge eth0
30: 0 2 397435013 1 0 3 0 0 PCI-MSI-edge eth1
31: 0 1 1 0 0 0 0 0 PCI-MSI-edge
32: 0 0 0 0 0 0 2 0 PCI-MSI-edge
33: 1 1 0 0 0 0 0 0 PCI-MSI-edge
34: 0 0 0 1 0 1 0 0 PCI-MSI-edge
35: 0 0 0 1 0 0 0 1 PCI-MSI-edge
36: 0 0 0 0 1 0 0 1 PCI-MSI-edge
37: 1 0 0 0 0 1 0 0 PCI-MSI-edge
38: 0 0 1 0 1 0 0 0 PCI-MSI-edge
39: 0 0 2 0 0 0 0 0 PCI-MSI-edge
40: 0 0 0 0 0 0 2 0 PCI-MSI-edge
41: 0 2 0 0 0 0 0 0 PCI-MSI-edge
42: 0 0 0 0 0 2 0 0 PCI-MSI-edge
43: 0 0 0 2 0 0 0 0 PCI-MSI-edge
44: 0 0 0 0 0 0 0 2 PCI-MSI-edge
45: 2 0 0 0 0 0 0 0 PCI-MSI-edge
46: 0 0 0 0 2 0 0 0 PCI-MSI-edge
48: 27752 16448 16392 27774 27930 27840 27924 27682 PCI-MSI-edge ahci
49: 0 1 1 0 0 2 1 0 PCI-MSI-edge ioat-msi
NMI: 782553 42565381 41948876 237091 359662 364201 202206 225406 Non-maskable interrupts
LOC: 5930454 449441826 428536599 2360476 2083086 2115135 2415493 2116945 Local timer interrupts
RES: 1714 1382 1944 904 810 720 1051 907 Rescheduling interrupts
CAL: 32 98 100 100 103 98 100 97 Function call interrupts
TLB: 1559 2476 19393 18806 1510 1870 21071 22096 TLB shootdowns
SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
ERR: 0
MIS: 0
next prev parent reply other threads:[~2009-06-30 8:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 16:06 weird problem Paweł Staszewski
2009-06-25 16:33 ` Paweł Staszewski
2009-06-25 17:18 ` Paweł Staszewski
2009-06-25 19:45 ` Paweł Staszewski
2009-06-25 20:18 ` Eric Dumazet
2009-06-25 22:23 ` Paweł Staszewski
2009-06-26 8:37 ` Jarek Poplawski
2009-06-26 9:05 ` Jarek Poplawski
2009-06-26 10:19 ` Eric Dumazet
2009-06-26 17:45 ` Paweł Staszewski
2009-06-26 17:57 ` Paweł Staszewski
2009-06-30 6:40 ` Jarek Poplawski
2009-06-30 8:35 ` Paweł Staszewski
2009-06-30 8:36 ` Paweł Staszewski [this message]
2009-07-08 22:34 ` Jarek Poplawski
2009-07-09 23:14 ` Paweł Staszewski
2009-07-09 23:59 ` Paweł Staszewski
2009-07-10 14:47 ` Jarek Poplawski
2009-07-11 6:24 ` Jarek Poplawski
2009-07-13 23:26 ` Paweł Staszewski
2009-07-14 16:24 ` Jarek Poplawski
2009-07-15 20:15 ` Paweł Staszewski
2009-07-15 22:43 ` Jarek Poplawski
2009-07-16 11:01 ` Jarek Poplawski
-- strict thread matches above, loose matches on Subject: below --
2003-10-14 11:00 Weird problem Jean-Rene Cormier
[not found] ` <3F8BEAEB.1060005@Loudoun-Fairfax.com>
[not found] ` <1066136413.12935.43.camel@forbidden.cipanb.ca>
2003-10-14 15:31 ` Jeffrey Laramie
[not found] ` <3F8C1700.3070902@Loudoun-Fairfax.com>
2003-10-14 16:59 ` Jean-Rene Cormier
2003-10-14 17:49 ` Jeffrey Laramie
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=4A49CE8B.7080402@itcare.pl \
--to=pstaszewski@itcare.pl \
--cc=dada1@cosmosbay.com \
--cc=eric.dumazet@gmail.com \
--cc=jarkao2@gmail.com \
--cc=netdev@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 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.