mirror of https://github.com/mkerrisk/man-pages
minor changes.
This commit is contained in:
parent
53255c2be2
commit
ffe649e940
|
@ -112,13 +112,12 @@ On Linux, programs that use the Pthreads API should be compiled using
|
|||
.SS "Linux Implementations of POSIX Threads"
|
||||
Over time, two threading implementations have been provided by
|
||||
the GNU C library on Linux:
|
||||
.IP \- 3
|
||||
.TP
|
||||
.B LinuxThreads
|
||||
This is the original Pthreads implementation.
|
||||
Since glibc 2.4, this implementation is no longer supported.
|
||||
.IP \- 3
|
||||
.B NPTL
|
||||
(Native POSIX Threads Library)
|
||||
.TP
|
||||
.BR NPTL " (Native POSIX Threads Library)"
|
||||
This is the modern Pthreads implementation.
|
||||
By comparison with LinuxThreads, NPTL provides closer conformance to
|
||||
the requirements of the POSIX.1 specification and better performance
|
||||
|
@ -128,7 +127,6 @@ and requires features that are present in the Linux 2.6 kernel.
|
|||
.PP
|
||||
Both of these are so-called 1:1 implementations, meaning that each
|
||||
thread maps to a kernel scheduling entity.
|
||||
|
||||
Both threading implementations employ the Linux
|
||||
.BR clone (2)
|
||||
system call.
|
||||
|
@ -247,7 +245,7 @@ NPTL does not employ a manager thread.
|
|||
NPTL makes internal use of the first two real-time signals;
|
||||
these signals cannot be used in applications.
|
||||
|
||||
NPTL still has a few non-conformances with POSIX.1:
|
||||
NPTL still has at least one non-conformance with POSIX.1:
|
||||
.IP \- 3
|
||||
Threads do not share a common nice value.
|
||||
.\" FIXME . bug report filed for NPTL nice non-conformance
|
||||
|
|
Loading…
Reference in New Issue