Writing a multithreaded daemon process

[Jake Burkholder]

> If the daemon can somehow reside entirely inside the kernel, like NFS
> daemon, we can save those crossings.  But the daemon is a multi-threaded
> process and we have no kernel thread yet, so I do not know how to do
> better if possible.  Maybe all user filesystems have to live with this
> limitation.

There's kernel threads and then there's kernel threads.

kthread_create (see sys/kern/kern_kthread.c) will create a new process
which shares it's address space with the kernel; that might be what you
want.