public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Corey Minyard <minyard@acm.org>
Cc: Jean Delvare <jdelvare@suse.de>,
	torvalds@linux-foundation.org,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Martin Wilck <martin.wilck@ts.fujitsu.com>,
	OpenIPMI Developers <openipmi-developer@lists.sourceforge.net>,
	Gary Smith <gasmith@redhat.com>
Subject: Re: [PATCH 1/4] IPMI: Add parameter to limit CPU usage in kipmid
Date: Tue, 9 Mar 2010 12:13:59 -0800	[thread overview]
Message-ID: <20100309121359.40766d99.akpm@linux-foundation.org> (raw)
In-Reply-To: <4B96A633.2080207@acm.org>

On Tue, 09 Mar 2010 13:49:07 -0600
Corey Minyard <minyard@acm.org> wrote:

> Jean Delvare wrote:
> > Hi Corey, Linus,
> >
> > On Wednesday 03 March 2010 05:14:38 pm Corey Minyard wrote:
> >   
> >> From: Martin Wilck <martin.wilck@ts.fujitsu.com>
> >>
> >> In some cases kipmid can use a lot of CPU.  This adds a way to tune
> >> the CPU used by kipmid to help in those cases.  By setting
> >> kipmid_max_busy_us to a value between 100 and 500, it is possible to
> >> bring down kipmid CPU load to practically 0 without loosing too much
> >> ipmi throughput performance.  Not setting the value, or setting the
> >> value to zero, operation is unaffected.
> >>
> >> Signed-off-by: Martin Wilck <martin.wilck@ts.fujitsu.com>
> >> Cc: Jean Delvare <jdelvare@suse.de>
> >> Signed-off-by: Corey Minyard <cminyard@mvista.com>
> >> ---
> >> This patch has been discussed quite a bit, and I believe all issues with it
> >> have been resolved.  It's not great, but nobody has a better way to handle
> >> the problem.
> >>     
> >
> > I still can't see this patch in Linus' tree as of 2.6.34-rc1. It has been 
> > waiting for sooo long already, can we finally get it in? Linus, will you apply 
> > it? Or should it go through Andrew?
> >   
> It's already in Andrew's patches.  It would be good if this could go in 
> for 2.6.34, I think it has been through enough review and such.

yup, I have it queued for 2.6.34.  -rc1 caught me napping so some
scrambling is happening.


      reply	other threads:[~2010-03-09 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 16:14 [PATCH 1/4] IPMI: Add parameter to limit CPU usage in kipmid Corey Minyard
2010-03-09 12:05 ` Jean Delvare
2010-03-09 19:49   ` Corey Minyard
2010-03-09 20:13     ` Andrew Morton [this message]

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=20100309121359.40766d99.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=gasmith@redhat.com \
    --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 \
    --cc=torvalds@linux-foundation.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