... --- drivers/net/wireless/airo.c | 107 ++++++++++++++++++++++---------------------- 1 file changed, 54 ... ; struct task_struct *airo_thread_task; - struct semaphore sem; + struct mutex lock; wait_queue_head_t thr_wait; ...

linux-kernel - Daniel Walker - May 22 2008 - 19:21

... > > --- > drivers/net/wireless/airo.c | 107 > ++++++++++++++++++++++---------------------- 1 file changed ... apriv->jobs); > wake_up_interruptible(&apriv->thr_wait); > } else Mutexes are not allowed in interrupt ...

linux-kernel - Michal Schmidt - May 26 2008 - 13:29

... dwalker@mvista.com> > > > > --- > > drivers/net/wireless/airo.c | 107 > > ++++++++++++++++++++++---------------------- 1 file ... jobs); > > wake_up_interruptible(&apriv->thr_wait); > > } else > > > Mutexes are not allowed in interrupt ...

linux-kernel - Daniel Walker - May 26 2008 - 13:59

... ad-hoc, with most references to ->sem being > unbalanced. It should ... 't be any case where semaphore behavior is used or needed ... instead of a > mutex. I'd want to study the driver ... on the mark already. Dan -- To unsubscribe from this list: send ...

linux-kernel - Dan Williams - May 27 2008 - 09:48

... 2008 03:29:14 Michal Schmidt wrote: > > > Mutexes are not allowed in interrupt context, ... me. I asked before to no response... > > Because mutexes have an owner. In ... type of usage on principal . Daniel -- To unsubscribe from this list: send the ...

linux-kernel - Daniel Walker - May 27 2008 - 00:34

... 2008 03:29:14 Michal Schmidt wrote: > > > Mutexes are not allowed in interrupt context, not ... to me. I asked before to no response... > > Because mutexes have an owner. In ... it seems like mutex_trylock_irq would be easy to add if needed, if only for ...

linux-kernel - Rusty Russell - May 27 2008 - 00:37

... 03:29:14 Michal Schmidt wrote: > > > > Mutexes are not allowed in interrupt context, ... me. I asked before to no response... > > > > Because mutexes have an owner. In ... possibly take such a retrograde step." -- To unsubscribe from this list: send the ...

linux-kernel - Matthew Wilcox - May 27 2008 - 07:24

... 2008 03:29:14 Michal Schmidt wrote: > > Mutexes are not allowed in interrupt context, ... me. I asked before to no response... Because mutexes have an owner. In ... t possibly take such a retrograde step." -- To unsubscribe from this list: send the line ...

linux-kernel - Matthew Wilcox - May 26 2008 - 22:15

... 2008 03:29:14 Michal Schmidt wrote: > Mutexes are not allowed in interrupt context, ... before to no response... Thanks, Rusty. -- To unsubscribe from this list: send the line " ... " in the body of a message to majordomo@vger.kernel.org More majordomo ...

linux-kernel - Rusty Russell - May 26 2008 - 21:17

... ad-hoc, with most references to ->sem being unbalanced. The driver ... instead of a mutex. I'd want to study the driver ... operating system, but compare it to ours. We can't possibly take such a retrograde step." -- To unsubscribe from this list: send ...

linux-kernel - Matthew Wilcox - May 27 2008 - 09:13

... Yeah, that might be the right way to go. If you want to ... I don't think you need to go into too much > detail with ... like the trylocking is just an optimization to save a wakeup .. Daniel ... in the body of a message to majordomo@vger.kernel.org More ...

linux-kernel - Daniel Walker - May 27 2008 - 11:08

... trylocking is just an optimization to save a wakeup .. 'just'? I ... operating system, but compare it to ours. We can't possibly ... take such a retrograde step." -- To unsubscribe from this list: send ... the body of a message to majordomo@vger.kernel.org More ...

linux-kernel - Matthew Wilcox - May 27 2008 - 11:34

... trylocking is just an optimization to save a wakeup .. > > 'just'? I ... performance reductions if you had to > do a wakeup for every ... d think we would have to know more about how it ... an unlikely case tho.. Daniel -- To unsubscribe from this list: send ...

linux-kernel - Daniel Walker - May 27 2008 - 12:01