Date: Thu, 17 Apr 2003 12:24:12 +0400 From: "Sergey A. Osokin" <osa@freebsd.org.ru> To: John Polstra <jdp@polstra.com> Cc: freebsd-threads@freebsd.org Subject: Re: FWD: Re: May I add pthread_[gs]etconcurrency to the threads libr Message-ID: <20030417082412.GA67305@freebsd.org.ru> In-Reply-To: <XFMail.20030416094409.jdp@polstra.com> References: <XFMail.20030416094409.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@pcnet1.pcnet.com> > To: John Polstra <jdp@polstra.com> > Subject: Re: May I add pthread_[gs]etconcurrency to the threads libraries? > Cc: deischen@freebsd.org, jeff@freebsd.org, freebsd-threads@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 / \
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030417082412.GA67305>