May I add pthread_[gs]etconcurrency to the threads libraries

[John Polstra]

Daniel Eischen wrote:
> On Wed, 16 Apr 2003, John Polstra wrote:
> 
>> Hi Guys,
>> 
>> Sergey Osokin sent me patches to add the standard
>> pthread_[gs]etconcurrency functions to our various threads
>> libraries.  I reviewed them and they're OK.  The functions don't do
>> anything significant, but they fill the need for this part of the
>> API.
>> 
>> OK if I commit them this weekend?  The changes don't change anything
>> else.  They just add stuff.
> 
> I'm about to implement them for real in libpthread.  I'd appreciate
> you not adding them to that.  I've got a slew of other changes that
> I want add to it very soon.

OK, I'm glad I asked. :-)  Please take what you can from Sergey's
patch, and credit him appropriately:

    http://ozz.pp.ru/patches/patch-pthread.2

There's a man page in there you should be able to use, at least.

> They don't seem to make sense for libthr and libc_r unless it
> returns ENOTSUP.  libthr is 1:1, so it is meaning less there
> as well as libc_r.

They're not allowed to return ENOTSUP.  The Single Unix
Specification says that if they're not implemented they must return
success after doing nothing.

John