Messages in this thread |  | | Date | Wed, 9 May 2001 09:59:00 -0400 (EDT) | From | "Richard B. Johnson" <> | Subject | Re: your mail |
| |
On Tue, 8 May 2001, Jens Axboe wrote:
> On Tue, May 08 2001, Richard B. Johnson wrote: > > > Use a kernel thread? If you don't need to access user space, context > > > switches are very cheap. > > > > > > > So, what am I supposed to do to add a piece of driver code to the > > > > run queue so it gets scheduled occasionally? > > > > > > Several, grep for kernel_thread. > > > > > > -- > > > Jens Axboe > > > > > > > Okay. Thanks. I thought I would have to do that too. No problem. > > A small worker thread and a wait queue to sleeep on and you are all set, > 10 minutes tops :-) > > > It's a "tomorrow" thing. Ten hours it too long to stare at a > > screen. > > Sissy! >
Okay. I am now awake. I will now try the kernel thread. Looks simple. Got to remember to kill it before/during module removal.
Cheers, Dick Johnson
Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of course you get it all back when you reboot..."; Actual explanation obtained from the Micro$oft help desk.
- 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/
|  |