linux-kernel - Re: [PATCH 1/4] IPMI: Add parameter to limit CPU usage in kipmid

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20100309121359.40766d99.akpm@linux-foundation.org>
Date:	Tue, 9 Mar 2010 12:13:59 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Corey Minyard <minyard@....org>
Cc:	Jean Delvare <jdelvare@...e.de>, torvalds@...ux-foundation.org,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Martin Wilck <martin.wilck@...fujitsu.com>,
	OpenIPMI Developers <openipmi-developer@...ts.sourceforge.net>,
	Gary Smith <gasmith@...hat.com>
Subject: Re: [PATCH 1/4] IPMI: Add parameter to limit CPU usage in kipmid

On Tue, 09 Mar 2010 13:49:07 -0600
Corey Minyard <minyard@....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@...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@...fujitsu.com>
> >> Cc: Jean Delvare <jdelvare@...e.de>
> >> Signed-off-by: Corey Minyard <cminyard@...sta.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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/