Gortmaker.
*
+ * Change cli()/sti() to SMP safe spin_lock_irqsave()
+ * /spin_unlock_irqrestore() calls, Yong Chi.
+ * Oct-10-2000 [EMAIL PROTECTED]
*
* This file is subject to the terms and conditions of the GNU General Public
* License. See the file COPYING in the main
Hopefully this will do for SMP locks. =)
Todo list also said that on UP, sleep_on() use is unsafe. It uses
"interruptible_sleep_on()" and "wake_up_interruptible()" calls. Are they
not safe on UP?
Thanks
--- ds.c.bakWed Oct 11 13:05:16 2000
+++ ds.cThu Oct 12 11:25:20 2000
@@
Take 2 based on semaphore -)
Jan-Simon Pendry wrote:
holding a spin lock across a (potential) sleep is a bug - it can
lead to deadlock.
jan-simon.
Jakub Jelinek wrote:
On Thu, Oct 12, 2000 at 11:38:11AM -0400, Yong Chi wrote:
Hopefully this will do for SMP locks. =)
Holding
Gortmaker.
*
+ * Change cli()/sti() to SMP safe spin_lock_irqsave()
+ * /spin_unlock_irqrestore() calls, Yong Chi.
+ * Oct-10-2000 <[EMAIL PROTECTED]>
*
* This file is subject to the terms and conditions of the GNU General Public
* License. See the file COPYING in th
Hopefully this will do for SMP locks. =)
Todo list also said that on UP, sleep_on() use is unsafe. It uses
"interruptible_sleep_on()" and "wake_up_interruptible()" calls. Are they
not safe on UP?
Thanks
--- ds.c.bakWed Oct 11 13:05:16 2000
+++ ds.cThu Oct 12 11:25:20 2000
@@
Take 2 based on semaphore -)
Jan-Simon Pendry wrote:
> holding a spin lock across a (potential) sleep is a bug - it can
> lead to deadlock.
>
> jan-simon.
>
> Jakub Jelinek wrote:
> >
> > On Thu, Oct 12, 2000 at 11:38:11AM -0400, Yong Chi wrote:
> > &g
6 matches
Mail list logo