DragonFly kernel List (threaded) for 2003-11
Re: messaging questions...
Matthew Dillon wrote:
:Cool.... So I have been gleefully digging through the thread code as it
:seems important to
:understand that before trying to message a thread :)... I noticed the
:kernel has a way to get
:the current thread very easily via some macros and functions.
:Is there any way a user can just find out what his current thread is?
:I presume every process
:has at least 1 of these things or a lot of what I am reading in the
:kernel doesn't look like it
:would work very well.
Each user process has only one kernel thread. That is, DFly is not
organized like the KSE model in FreeBSD-5. DFly's organization
is very simple by comparison because the intention with DFly is
to have to userland manage userland threads entirely within
If that makes any sense :-)
And also, a thread can be standalone and not linked to a
process. Watch out for this one David, it bites the ass
very badly. :-)
Hiten Pandya (hmp@xxxxxxxxxxxxx)