linux-kernel - Re: [PATCH] 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] [thread-next>] [day] [month] [year] [list]

Message-Id: <200912191456.04950.jdelvare@suse.de>
Date:	Sat, 19 Dec 2009 14:56:04 +0100
From:	Jean Delvare <jdelvare@...e.de>
To:	minyard@....org
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Martin Wilck <martin.wilck@...fujitsu.com>,
	OpenIPMI Developers <openipmi-developer@...ts.sourceforge.net>
Subject: Re: [PATCH] IPMI: Add parameter to limit CPU usage in kipmid

Le jeudi 17 décembre 2009 23:08, Corey Minyard a écrit :
> I cleaned up the patch some.  I added some state results to the list of
> things to be busy waited for (should improve performance a bit) and
> changed the schedule_timeout_interruptible back to 1, since that's
> what it's supposed to be.  And I added some comments.

Thanks for doing this!

> I did some testing on my system here.  On my system, kipmid uses almost
> no CPU normally.  If I set the kipmid_max_busy_us value to 500, the
> interface was more than 5 times slower.  I had to set the value up to
> 35000 for it to go back to the normal performance, and it was pretty
> linear between the two values.  So this is definiately not for all
> systems.
> 
> Can you try this out to make sure its ok?

I don't have any hardware where I can test this myself. But hopefully
Martin does?

Thanks,
-- 
Jean Delvare
Suse L3
--
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/