[484] in Pthreads mailing list archive
Re: New Pthreads Book
daemon@ATHENA.MIT.EDU (Bob Knighten)
Tue Nov 5 16:31:26 1996
Date: Tue, 5 Nov 96 12:49:49 PST
From: Bob Knighten <knighten@co.intel.com>
To: colohan@eecg.toronto.edu
Cc: pthreads@MIT.EDU
In-Reply-To: <96Nov4.175056est.35(2)@picton.eecg.toronto.edu>
Reply-To: knighten@co.intel.com (Bob Knighten)
Chris Colohan writes:
> ... <text deleted> ...
>
> The book claims to cover Posix 1003.1c -- is this the same version of
> the standard that MIT-Pthreads is coded to? Is it reasonable for me
> to expect Pthreads to behave in the same manner as outlined in this
> book, especially when it comes to signal handling etc?
>
There is only one standard (in gory detail ISO/IEC 9945-1:1996(E), ANSI/IEEE
Std 1003.1, 1996 Edition, Information technology -- Portable Operating System
Interface (POSIX) -- Part 1: System Application Program Interface (API) [C
Language]). This is the entire POSIX system interface with Pthreads included
there is no separate Pthreads standard. While the Pthreads standard was under
development the draft standard was known as P1003.4a, and then P1003.1c. The
draft standard has been stable for a couple of years now and it is this stable
draft that was clearly used when writing the book.
> If so, I have found a couple of small (trivial) bugs in Pthreads:
> - The structure element sched_param.prio should be named
> sched_param.sched_priority.
Indeed. The only required field in the structure sched_param is sched_priority.
> - The functions sched_get_priority_max() and sched_get_priority_min()
> seem to be missing...
These are actually only required if {_POSIX_PRIORITY_SCHEDULING} is defined.
>
> ... <more text deleted> ...
--
Robert L. Knighten | knighten@co.intel.com
Server Architecture Lab |
Intel Corporation |
5200 N.E. Elam Young Parkway, CO3-202 | (503) 677-4315
Hillsboro, OR 97124-6497 | (503) 677-6700 [FAX]
