Messages in this thread | | | Date | Tue, 26 Feb 2002 15:17:27 -0500 (EST) | From | "Richard B. Johnson" <> | Subject | Re: schedule() |
| |
On Tue, 26 Feb 2002, Davide Libenzi wrote:
> On Tue, 26 Feb 2002, Richard B. Johnson wrote: > > > > > > > I just read on this list that: > > > > while(something) > > { > > current->policy |= SCHED_YIELD; > > schedule(); > > } > > > > Will no longer be allowed in a kernel module! If this is true, how > > do I loop, waiting for a bit in a port, without wasting CPU time? > > > > A lot of hardware does not generate interrupts upon a condition, > > there is no CPU activity that could send a wake_up_interruptible() > > to something sleeping. > > > > For instance, I need to write data to a hardware FIFO, one long-word > > at a time, but I can't just write. I have to wait for a bit to be > > set or reset for each and every write. I'm going to be burning a > > lot of CPU cycles if I can't schedule() while the trickle-down-effect > > of the hardware is happening. > > What did it do yield() to you ? Doesn't it work for your case ? > There isn't one in 2.4.x I'll modify my drivers to use YIELD and #define it depending upon version.
Cheers, Dick Johnson
Penguin : Linux version 2.4.1 on an i686 machine (797.90 BogoMips).
111,111,111 * 111,111,111 = 12,345,678,987,654,321
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |