On Thu, 2009-11-26 at 13:44 +0200, Peter Ujfalusi wrote: > On Thursday 26 November 2009 12:18:59 ext Mark Brown wrote: > > On Thu, Nov 26, 2009 at 11:31:15AM +0200, Peter Ujfalusi wrote: > > > For a quick fix, I can convert the tlv320dac33 driver to use this, and > > > revisit later, if it does not fulfill the timing requirements for the HW. > > > > If there are problems then creating a dedicated thread you can wake > > would probably do the job. > > For now I'm going to change the create_rt_workqueue to > create_singlethread_workqueue, that is available at the wq.git of kernel.org. > > If it is not sufficient, than I might use dedicated thread, which I woke up, but > I would like to keep that as a backup plan, since it needs more work ;) Peter, I would suspect using a single-threaded workqueue is better than a wake_up() of another thread. IIRC, after queuing work, the workqueue's single thread may run almost immediately on the same processor. With waking up sleeping threads, I've run into scheduler delays around 10 ms on a dual core x86_64 desktop system. Regards, Andy > I'll send the patch in a few minutes. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
