Re: [PATCH] Msleep_interruptible() on a dual processor system may wait a long time.

2013-04-30 Thread Srivatsa S. Bhat
On 04/30/2013 06:50 AM, David VomLehn wrote: > Msleep_interruptible() on a dual processor system may wait a long time. > > On some reboots, calling msleep_interruptible() from CPU 1 on a dual > processor system will not return for seconds or even minutes. This happens > because ksoftirqd/1 migrate

Re: [PATCH] Msleep_interruptible() on a dual processor system may wait a long time.

2013-04-29 Thread Steven Rostedt
This should have been Cc'd to the scheduler maintainers. -- Steve On Mon, Apr 29, 2013 at 06:20:28PM -0700, David VomLehn wrote: > Msleep_interruptible() on a dual processor system may wait a long time. > > On some reboots, calling msleep_interruptible() from CPU 1 on a dual > processor system w

[PATCH] Msleep_interruptible() on a dual processor system may wait a long time.

2013-04-29 Thread David VomLehn
Msleep_interruptible() on a dual processor system may wait a long time. On some reboots, calling msleep_interruptible() from CPU 1 on a dual processor system will not return for seconds or even minutes. This happens because ksoftirqd/1 migrates to CPU 0, which is allowed because its cpus_allowed m