public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: minyard@acm.org, Linux Kernel <linux-kernel@vger.kernel.org>,
	Martin Wilck <martin.wilck@ts.fujitsu.com>,
	Jean Delvare <jdelvare@suse.de>,
	OpenIPMI Developers <openipmi-developer@lists.sourceforge.net>
Subject: Re: [PATCH] IPMI: Add parameter to limit CPU usage in kipmid
Date: Thu, 17 Dec 2009 10:12:22 +0300	[thread overview]
Message-ID: <4B29D9D6.9030702@msgid.tls.msk.ru> (raw)
In-Reply-To: <20091216134252.868ea5bf.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Wed, 16 Dec 2009 15:23:54 -0600
> Corey Minyard <minyard@acm.org> wrote:
> 
>> From: Martin Wilck <martin.wilck@ts.fujitsu.com>
>>
>> In some cases kipmid can use a lot of CPU.
> 
> Why is that?  Without this information it is hard for others to suggest
> alternative implementations.

[picking up the thread from the middle]

I dunno why, but I can confirm that kipmid is one of the most
noticeable threads on all machines here running ipmid.

Here's an example from a machine with 20days uptime.
According to `ps -aflx', [kipmid] process took 30:34
sec of CPU time.  Most close to that is [md6_raid1]
thread with 12:30, and next to that is [kjournald]
with 0:24.  30:34 is not exactly huge given 20days
uptime, but it is a clear "winner", far from the
most close competitor.

Different kernels, somewhat different hardware, but
the same behavour.

/mjt

  reply	other threads:[~2009-12-17  7:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 21:23 [PATCH] IPMI: Add parameter to limit CPU usage in kipmid Corey Minyard
2009-12-16 21:42 ` Andrew Morton
2009-12-17  7:12   ` Michael Tokarev [this message]
2009-12-17 10:36   ` Jean Delvare
2009-12-17 18:34     ` Corey Minyard
2009-12-17 20:07       ` Jean Delvare
2009-12-17 22:08         ` Corey Minyard
2009-12-19 13:56           ` Jean Delvare
2010-01-14 14:02             ` Jean Delvare

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=4B29D9D6.9030702@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=akpm@linux-foundation.org \
    --cc=jdelvare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.wilck@ts.fujitsu.com \
    --cc=minyard@acm.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    /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