Corey Minyard wrote: > I would guess that changing the nice value is the main thing that caused > the difference. The other changes probably didn't make as big a difference.
That's true, but setting the nice level to 0 isn't "nice" without kipmid_max_busy. The two parameters help to make sure that kipmid doesn't use excessive CPU time. I am not sure about your reasons to call schedule() in every loop iteration. If there is no other process that needs to run, it will just waste cycles trying to figure that out. If there are other processes, you say yourself that "kipmid would never be scheduled in a busy system". Does it really make sense to call schedule() every microsecond? That's what kipmid effectively does if it waits for the KCS interface, because it'll do a port_inb() in every iteration which takes ca. 1us. > I'm ok with tuning like this, but most users are probably not going to > want this type of behavior. Let's wait and see :-) Martin -- Martin Wilck PRIMERGY System Software Engineer FSC IP ESP DEV 6 Fujitsu Siemens Computers GmbH Heinz-Nixdorf-Ring 1 33106 Paderborn Germany Tel: ++49 5251 525 2796 Fax: ++49 5251 525 2820 Email: mailto:[email protected] Internet: http://www.fujitsu-siemens.com Company Details: http://www.fujitsu-siemens.com/imprint.html ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Openipmi-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openipmi-developer
