DragonFly kernel List (threaded) for 2003-07
Re: Call for Developers! Userland threading
:> hahahaha. dragonthread... hahahaha.
:> lwkt_thread is good for userland. I was going to call the kernel
:> thread's lwkt_thread but I decided to stick with the 5.x 'thread'
:light weight kernel thread _ thread? what about
:lwkt in kernel
:lwut in userspace or just lwt?
Just lwkt_thread I think. Sure there's a little pollution but it's
better to have pollution then confusion.
Besides, who says we wouldn't eventually be running whole kernels in
userland? Then the userland LWKT's would deserve the 'K'.
:The upcall system of KSE seems like the best way to preempt a process for
:signals. Even though there should only be one message port from what I
:understand, what about 2, and having one do an upcall for things which need
:immediate attention? If im misunderstanding and every time a message is
:receive it jumps to a handler just ignore me.
An upcall is probably the best way, though as with our IPI messaging
the kernel would not necessary *have* to always upcall, it could just
queue the returned message and let the userland pick it up in its own