Defect Report concerning: IEEE Std. 1003.1c-1995, ISO/IEC 9945-1:1990 AMD 2 - Threads
Clause: ??
PASC Interpretation Ref: pasc-1003.1c-07
Topic: PTHREAD_INHERIT_SCHED

This is an unapproved interpretation of PASC 1003.1c-1995, ISO/IEC 9945-1:1990 AMD 2 - Threads.

Use of the information contained in this unapproved document is at your own risk.

Last update: 30 March,1998 

								1003.1c-95  #7

 _____________________________________________________________________________

	Interpretation Number:	XXXX
	Topic:               PTHREAD_INHERIT_SCHED
	Relevant Sections:   ??

Interpretation Request: (Defect Report)
-----------------------



From: eliot@dg-rtp.dg.com (Topher Eliot)
Date: Wed, 17 Apr 1996 11:22:42 -0400 (EDT)

Greetings:

This is a request for interpretation on an issue in the forthcoming
POSIX 1003.1c, presumably 1996.  Right now all I have to work from are
the draft 8 document, plus the draft 9 and 10 change documents, 
but draft 10 was approved as the final specification.

My question concerns section 13.5.1.1 in draft 8 (lines 302-306)  This
text was not modified by the drafts 9 or 10 changes documents.

When a thread is created with a value of PTHREAD_INHERIT_SCHED for the
inheritsched attribute, is the scheduling contention scope one of the
atributes that is inherited?  Or should the new thread get the
implementation-defined default scheduling contention scope?


Interpretation response
------------------------

The standard is clear: contentionscope is one of the attributes 
controlled by inheritsched.
P1003.1c-1995 page 296 line 397 states: 
    "The contentionscope attribute defines the scheduling ...."
and on line 401 the standard uses this fact
    ".....set according to the other scheduling attributes in 
pthread_attr_t object."

Rationale
-------------
None.
Forwarded to Interpretations group: May 28 1996
Finalised: July 10th 1996.