linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: danial_thom@yahoo.com
Cc: Erik Mouw <erik@harddisk-recovery.com>, linux-kernel@vger.kernel.org
Subject: Re: Measuring tools - top and interrupts
Date: Fri, 23 Jun 2006 10:32:23 +0200	[thread overview]
Message-ID: <1151051543.11381.43.camel@Homer.TheSimpsons.net> (raw)
In-Reply-To: <20060622233744.99206.qmail@web33314.mail.mud.yahoo.com>

On Thu, 2006-06-22 at 16:37 -0700, Danial Thom wrote:
> I'm sorry, but you're being an idiot if you think
> that 16K interrupts per second and forwarding 75K
> pps generate no cpu load. Its just that simple.
> It also means that you've never profiled a kernel
> because you don't understand where the loads are
> generated. You've probably been on too many lists
> with too many people who have no idea what
> they're talking about.

(what horrid manners)

Hm.  You may be right about the load average calculation being broken.

Below is a 100 second profile sample of my 3GHz P4 handling 15K
interrupts per second while receiving a flood ping.  My interpretation
is that tools should be showing ~10% cpu load rather than zero.  Am I'm
misinterpreting it?

 97574 total                                      0.0258
 89549 default_idle                             1017.6023
  1734 ioread16                                  36.8936
  1138 ioread8                                   24.7391
   974 rhine_start_tx                             1.3994
   534 __do_softirq                               3.8417
   331 handle_IRQ_event                           3.2772
   223 rhine_interrupt                            0.0739
   222 memset                                     7.9286
   194 nf_iterate                                 1.5520
   140 local_bh_enable                            1.0769
    99 __kmalloc                                  1.0532
    92 net_rx_action                              0.2000
    85 kfree                                      0.9884
    82 skb_release_data                           0.6406
    77 csum_partial_copy_generic                  0.3105
    73 ip_push_pending_frames                     0.0681
    71 __alloc_skb                                0.2898
    69 kmem_cache_free                            1.3529
    66 kmem_cache_alloc                           1.3750
    62 csum_partial                               0.2153
    61 rt_hash_code                               0.4959
    61 ip_append_data                             0.0253
    60 netif_receive_skb                          0.0516
    58 ip_rcv                                     0.0471
    58 ip_local_deliver                           0.0854
    58 eth_type_trans                             0.2489
    55 ip_output                                  0.0957
    52 icmp_reply                                 0.1187



  reply	other threads:[~2006-06-23  8:28 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 15:26 Measuring tools - top and interrupts Danial Thom
2006-06-22 16:19 ` Randy.Dunlap
2006-06-22 17:16   ` Bernd Eckenfels
2006-06-22 16:21 ` Erik Mouw
2006-06-22 16:58   ` Danial Thom
2006-06-22 17:31     ` Erik Mouw
2006-06-22 23:37       ` Danial Thom
2006-06-23  8:32         ` Mike Galbraith [this message]
2006-06-23 20:14           ` Danial Thom
2006-06-23 22:51             ` Mike Galbraith
2006-06-23  9:02         ` Erik Mouw
2006-06-23 17:13         ` Alistair John Strachan
2006-06-23 18:16           ` Danial Thom
2006-06-23  5:34       ` sena seneviratne
2006-06-23 20:42       ` Danial Thom
2006-06-22 17:57     ` Francois Romieu
2006-06-22 22:47       ` Danial Thom
2006-06-22 23:53         ` Francois Romieu
2006-06-23 20:34           ` Danial Thom
2006-06-23 21:19             ` Francois Romieu
2006-06-24  2:07     ` Björn Steinbrink
2006-06-24  4:39       ` sena seneviratne
2006-06-24  5:59     ` Mike Galbraith
2006-06-24  6:26       ` Mike Galbraith
2006-06-24  9:21         ` Björn Steinbrink
2006-06-24  9:51           ` Mike Galbraith
2006-06-24 11:41             ` Mike Galbraith
2006-06-24 15:40               ` Björn Steinbrink
2006-06-24 16:23                 ` Mike Galbraith
2006-06-24 19:25                   ` Björn Steinbrink
2006-06-25  5:06                     ` Mike Galbraith
2006-06-25 11:12                       ` Björn Steinbrink
2006-06-25 14:24                         ` [PATCH] i386: Fix softirq accounting with 4K stacks Björn Steinbrink
2006-06-25 15:15                           ` Arjan van de Ven
2006-06-25 17:44                           ` Mike Galbraith
2006-06-25 17:43                             ` Arjan van de Ven
2006-06-25 18:42                               ` Björn Steinbrink
2006-06-26  2:23                                 ` Mike Galbraith
2006-06-26  3:05                                   ` Mike Galbraith
2006-06-26 17:58                                     ` Björn Steinbrink
2006-06-27 10:09                                       ` Mike Galbraith
2006-06-25 20:45                         ` Measuring tools - top and interrupts Danial Thom
2006-06-26  2:33                           ` Mike Galbraith
2006-06-30 13:41                             ` Danial Thom
2006-06-30 18:03                               ` Mike Galbraith

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=1151051543.11381.43.camel@Homer.TheSimpsons.net \
    --to=efault@gmx.de \
    --cc=danial_thom@yahoo.com \
    --cc=erik@harddisk-recovery.com \
    --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;
as well as URLs for NNTP newsgroup(s).