Thread VS process

[Pallav singh]

Hi

Posix threads library is used as portable library across different OS
Platform
API provided by Posix will map to different Thread API provided by OS
on which
Our Application is running ( Using Posix Thread Library ). Hence Api
like thread
creation, Scheduling , synchronization mechanism…. Will map to OS call
doing this.

Is there any Thread Library , which does scheduling on it own ? For
OS it should have
only Information on Process, it does not have any idea of threads
inside Process

Thanks
Pallav Singh

 

[Keith Thompson]

Posix threads library is used as portable library across different OS
Platform API provided by Posix will map to different Thread API
provided by OS on which Our Application is running ( Using Posix
Thread Library ). Hence Api like thread creation, Scheduling ,
synchronization mechanism…. Will map to OS call doing this.

Is there any Thread Library , which does scheduling on it own ? For OS
it should have only Information on Process, it does not have any idea
of threads inside Process

You'll probably get better information in comp.programming.threads.

 

[Ersek, Laszlo]

Posix threads library is used as portable library across different OS
Platform API provided by Posix will map to different Thread API provided
by OS on which Our Application is running ( Using Posix Thread Library
). Hence Api like thread creation, Scheduling , synchronization
mechanism?. Will map to OS call doing this.

Is there any Thread Library , which does scheduling on it own ? For OS
it should have only Information on Process, it does not have any idea of
threads inside Process

http://en.wikipedia.org/wiki/GNU_Portable_Threads
http://www.gnu.org/software/pth/

lacos

 

[Tom St Denis]

Is there  any Thread Library , which does scheduling on it own ? For
OS it should have
only Information on Process, it does not have any idea of threads
inside Process

You're basically asking about some sort of co-operative multitasking
done entirely inside the application at that point. Basically the
application in reality is one OS process but has multiple co-routines
which it switches between without OS intervention [e.g. timers or what
not to force switching, hence "co-operative"].

In general, on hosted platforms most people forgo that nightmare and
just use pthreads and/or multiple processes with IPC.

Also check out the other group that Keith pointed out.

Tom