On Tue, May 27, 2008 at 08:08:35AM -0700, Daniel Walker wrote: > > On Tue, 2008-05-27 at 09:48 -0400, Dan Williams wrote: > > > > Yeah, that might be the right way to go. If you want to jump into the > > driver, feel quite free, but I don't think you need to go into too much > > detail with it. Your overall behavior analysis is right on the mark > > already. > > I think we could just remove the trylock from the interrupt case, and > always force the wake_up_interruptible(&priv->thr_wait) case. It looks > like the trylocking is just an optimization to save a wakeup .. 'just'? I think you'd see severe performance reductions if you had to do a wakeup for every interrupt. -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
