hmmmm
>
>
> I don't follow. Linux _only_ has kernel-mode threads. Each
> thread is a
> unique process with its own PID and context. Linux is just
> real slick
> on doing the fork() by using the copy-on-write page-sharing
> trick...
>
apparently you can implement user mode threads in Linux too,
and that is what Netscape uses ... (this I am told)
so is there any way to tell that a thread is a thread and not
a child process or just a forked process in Linux? Other than
looking at the source code? ie -> does the task_struct keep this
info?
> But kernel-mode they are, and that is _all_ that you can do
> unless you
> write your own thread library. IE the pthreads library uses
> kernel-level
> processes for each thread...
>
>
>
> linux _never_ keeps all threads on the same cpu. Unless you
> only have one
> cpu...
>
>
really? so then Linux uses a sort of 'voluntary' thread
migration mechanism?
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
