This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: incorrect usage of cancellable nanosleep() in __pthread_acquire() ?
- From: Daniel Jacobowitz <drow at false dot org>
- To: Mike Frysinger <vapier at gentoo dot org>
- Cc: libc-ports at sourceware dot org
- Date: Wed, 25 Oct 2006 08:41:11 -0400
- Subject: Re: incorrect usage of cancellable nanosleep() in __pthread_acquire() ?
- References: <200610250611.40360.vapier@gentoo.org>
On Wed, Oct 25, 2006 at 06:11:39AM -0400, Mike Frysinger wrote:
> and noticed that nanosleep() is in there but pthread_mutex_lock() is not ...
> so, since pthread_mutex_lock() is implemented on top of __pthread_lock()
> which is implemented on top of __pthread_acquire() which calls nanosleep(),
> isnt this a not-so-good idea ? the huge comment block above
> __pthread_acquire() explains why this is necessary, and considering we have
> to do all this ugly scheduling in userspace while nptl does it in kernel
> space, i guess there's no way around it ?
Before I even look any closer at these reports, what's the point?
LinuxThreads is nothing even vaguely like POSIX compliant. It's never
claimed to be, and at this late date it certainly never will be.
--
Daniel Jacobowitz
CodeSourcery