* [PATCH] IPMI: Set schedule_timeout_wait value back to one
@ 2010-06-16 13:51 Corey Minyard
2010-06-16 20:32 ` Andrew Morton
0 siblings, 1 reply; 2+ messages in thread
From: Corey Minyard @ 2010-06-16 13:51 UTC (permalink / raw)
To: Linux Kernel, Andrew Morton; +Cc: Martin Wilck, Thomas Jarosch
From: Martin Wilck <martin.wilck@ts.fujitsu.com>
Some systems were seeing CPU usage go up dramatically with the recent
changes to try to reduce timer usage in the IPMI driver. This was
traced down to schedule_timeout_interruptible(1) being changed to
schedule_timeout_interruptbile(0). Revert that change.
Reported-by: Thomas Jarosch <thomas.jarosch@intra2net.com>
Signed-off-by: Corey Minyard <cminyard@mvista.com>
Tested-by: Thomas Jarosch <thomas.jarosch@intra2net.com>
---
Index: linux-2.6/drivers/char/ipmi/ipmi_si_intf.c
===================================================================
--- linux-2.6.orig/drivers/char/ipmi/ipmi_si_intf.c
+++ linux-2.6/drivers/char/ipmi/ipmi_si_intf.c
@@ -1018,7 +1018,7 @@ static int ipmi_thread(void *data)
else if (smi_result == SI_SM_IDLE)
schedule_timeout_interruptible(100);
else
- schedule_timeout_interruptible(0);
+ schedule_timeout_interruptible(1);
}
return 0;
}
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] IPMI: Set schedule_timeout_wait value back to one
2010-06-16 13:51 [PATCH] IPMI: Set schedule_timeout_wait value back to one Corey Minyard
@ 2010-06-16 20:32 ` Andrew Morton
0 siblings, 0 replies; 2+ messages in thread
From: Andrew Morton @ 2010-06-16 20:32 UTC (permalink / raw)
To: minyard; +Cc: Linux Kernel, Martin Wilck, Thomas Jarosch, stable
On Wed, 16 Jun 2010 08:51:44 -0500
Corey Minyard <minyard@acm.org> wrote:
> From: Martin Wilck <martin.wilck@ts.fujitsu.com>
>
> Some systems were seeing CPU usage go up dramatically with the recent
> changes to try to reduce timer usage in the IPMI driver. This was
> traced down to schedule_timeout_interruptible(1) being changed to
> schedule_timeout_interruptbile(0). Revert that change.
>
> Reported-by: Thomas Jarosch <thomas.jarosch@intra2net.com>
> Signed-off-by: Corey Minyard <cminyard@mvista.com>
> Tested-by: Thomas Jarosch <thomas.jarosch@intra2net.com>
> ---
>
> Index: linux-2.6/drivers/char/ipmi/ipmi_si_intf.c
> ===================================================================
> --- linux-2.6.orig/drivers/char/ipmi/ipmi_si_intf.c
> +++ linux-2.6/drivers/char/ipmi/ipmi_si_intf.c
> @@ -1018,7 +1018,7 @@ static int ipmi_thread(void *data)
> else if (smi_result == SI_SM_IDLE)
> schedule_timeout_interruptible(100);
> else
> - schedule_timeout_interruptible(0);
> + schedule_timeout_interruptible(1);
> }
> return 0;
> }
This fixes a regression introduced by ae74e823cb7d ("ipmi: add
parameter to limit CPU usage in kipmid"), yes? I noted that in the
changelog.
I also noted that it addresses
https://bugzilla.kernel.org/show_bug.cgi?id=16147 and I added the
vital(!) cc:stable@kernel.org, as we busted 2.6.34.
This is a pretty important -stable fix I think - several people have
hit it and the effects are ugly.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-06-16 20:33 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-06-16 13:51 [PATCH] IPMI: Set schedule_timeout_wait value back to one Corey Minyard
2010-06-16 20:32 ` Andrew Morton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox