All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Gallatin <gallatin@myri.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, robert@robur.slu.se
Subject: Re: CPU utilization increased in 2.6.27rc
Date: Wed, 13 Aug 2008 16:36:27 -0400	[thread overview]
Message-ID: <48A345CB.3090806@myri.com> (raw)
In-Reply-To: <87tzdoznqg.fsf@basil.nowhere.org>

Andi Kleen wrote:
> Andrew Gallatin <gallatin@myri.com> writes:
>> 8363      6.5081  vmlinux                  _raw_spin_lock
>> 5612      4.3672  oprofiled                (no symbols)
>> 4420      3.4396  ehci_hcd                 (no symbols)
>> 4325      3.3657  vmlinux                  handle_IRQ_event
>> 3688      2.8700  vmlinux                  default_idle
>> 3164      2.4622  vmlinux                  nv_start_xmit_optimized
>> 3092      2.4062  vmlinux                  sk_run_filter
>                                              ^^^^^^^^^^^^^
> 
> Looks like you have one of those nasty dhcpcds running that
> always open a raw socket and intercept everything using a filter?
> I always hoped those would disappear eventually and just
> bind to the proper protocol, but they seem to refuse dying.

Yeah, the box is running an ancient CENTOS4, so the dhcpcd
is pretty old.

Drew

  reply	other threads:[~2008-08-13 20:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-13  0:56 CPU utilization increased in 2.6.27rc Andrew Gallatin
2008-08-13  1:05 ` David Miller
2008-08-13 15:06   ` Andrew Gallatin
2008-08-13  1:15 ` David Miller
2008-08-13 16:13   ` Andrew Gallatin
2008-08-13 19:52     ` Robert Olsson
2008-08-13 21:34       ` Stephen Hemminger
2008-08-13 21:56         ` Robert Olsson
2008-08-13 22:06           ` Stephen Hemminger
2008-08-13 22:21             ` Robert Olsson
2008-08-13 20:03     ` Andi Kleen
2008-08-13 20:36       ` Andrew Gallatin [this message]
2008-08-13 20:27     ` David Miller
2008-08-13 20:58       ` Andrew Gallatin

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=48A345CB.3090806@myri.com \
    --to=gallatin@myri.com \
    --cc=andi@firstfloor.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=robert@robur.slu.se \
    /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.