FWD: Re: May I add pthread_[gs]etconcurrency to the threads libr

Sergey A. Osokin osa at freebsd.org.ru
Thu Apr 17 01:24:19 PDT 2003


On Wed, Apr 16, 2003 at 09:44:09AM -0700, John Polstra wrote:
> Sergey,
> 
> FYI -- Dan Eischen asked me not to commit your changes to
> libpthread.  I then told him he should at least try to use your man
> page and credit you appropriately.
> 
> I also told him that he's wrong about returning ENOTSUP, according
> to the standards.
> 
> John

So, I can't understand Daniel's position.
SUSV2 and SUSV3 says:
<quote>
If an implementation does not support multiplexing of user threads
on top of several kernel-scheduled entities, the
pthread_setconcurrency() and pthread_getconcurrency() functions
are provided for source code compatibility but they shall have no
effect when called.
</quote>

AFAIK at this time real implementation of that fuctions not yet avaliable.
If it not yet avaliable - I think we must use this implementation.
In near future, when the other implementations to be avaliable,
somebody immediatly replace old fake implementation with new real one.

> Date: Wed, 16 Apr 2003 12:35:57 -0400 (EDT)
> From: Daniel Eischen <eischen at pcnet1.pcnet.com>
> To: John Polstra <jdp at polstra.com>
> Subject: Re: May I add pthread_[gs]etconcurrency to the threads libraries?
> Cc: deischen at freebsd.org, jeff at freebsd.org, freebsd-threads at freebsd.org
> 
> On Wed, 16 Apr 2003, John Polstra wrote:
> 
> > 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.
> 
> 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.
> 
> -- 
> Dan Eischen

-- 

Rgdz,                        /"\  ASCII RIBBON CAMPAIGN
Sergey Osokin aka oZZ,       \ /    AGAINST HTML MAIL
http://ozz.pp.ru/             X          AND NEWS
                             / \


More information about the freebsd-threads mailing list