pour commencer, je peux me tromper dans ce que je dis, et je suis heureux de pouvoir discuter de ceci.
Je parlais bien cependant de la NPTL quand je disais que chaque thread etaient en fait encapsulé dans un process.
La NPTL semble surtout ensuite apporter certaine primitive de synchronisation entre les threads(process) crées.
j'ai tenu a verifier et dans WikiPedia http://en.wikipedia.org/wiki/NPTL
(qui bien sur n'est pas parole d'evengile, mais bon) je lis :
NPTL uses a similar approach to LinuxThreads, in that the primary abstraction known by the kernel is still a process, and new threads are created with the clone() system call (called from the NPTL library). However, NPTL requires specialized kernel support to implement (for example) the contended case of synchronisation primitives which might require threads to sleep and be re-awoken. The primitive used for this is known as a futex.
NPTL is a so-called ×ばつ1 threads library, in that threads created by the user (via the pthread_create() library function) are in 1-1 correspondence with schedulable entities in the kernel (processes, in the Linux case). This is the simplest possible threading implementation.
Maintenant je peux me meprendre sur certain point et je suis ouvert a toutes discussions.
[^] # Re: ...
Posté par brouillon . En réponse à la dépêche Erlang/OTP R11B supporte les architectures multiprocesseur. Évalué à 6.
Je parlais bien cependant de la NPTL quand je disais que chaque thread etaient en fait encapsulé dans un process.
La NPTL semble surtout ensuite apporter certaine primitive de synchronisation entre les threads(process) crées.
j'ai tenu a verifier et dans WikiPedia
http://en.wikipedia.org/wiki/NPTL
(qui bien sur n'est pas parole d'evengile, mais bon) je lis :
NPTL uses a similar approach to LinuxThreads, in that the primary abstraction known by the kernel is still a process, and new threads are created with the clone() system call (called from the NPTL library). However, NPTL requires specialized kernel support to implement (for example) the contended case of synchronisation primitives which might require threads to sleep and be re-awoken. The primitive used for this is known as a futex.
NPTL is a so-called ×ばつ1 threads library, in that threads created by the user (via the pthread_create() library function) are in 1-1 correspondence with schedulable entities in the kernel (processes, in the Linux case). This is the simplest possible threading implementation.
Maintenant je peux me meprendre sur certain point et je suis ouvert a toutes discussions.