public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail•com>
To: =?ISO-8859-2?Q?Pawe=B3_Staszewski?= <pstaszewski@itcare•pl>
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 06:40:22 +0000	[thread overview]
Message-ID: <20090630064022.GA5589@ff.dom.local> (raw)
In-Reply-To: <4A450955.1010806@itcare.pl>

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
...
> 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

  parent reply	other threads:[~2009-06-30  6:40 UTC|newest]

Thread overview: 24+ 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 [this message]
2009-06-30  8:35                   ` Paweł Staszewski
2009-06-30  8:36                     ` Paweł Staszewski
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

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=20090630064022.GA5589@ff.dom.local \
    --to=jarkao2@gmail$(echo .)com \
    --cc=dada1@cosmosbay$(echo .)com \
    --cc=eric.dumazet@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pstaszewski@itcare$(echo .)pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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