[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Interaction of pthreads and cthreads
From: |
Erik Verbruggen |
Subject: |
Re: Interaction of pthreads and cthreads |
Date: |
Tue, 1 May 2001 18:54:42 +0200 |
User-agent: |
Mutt/1.2.5i |
On Thu, Apr 26, 2001 at 04:38:22PM -0700, Jeff Bailey wrote:
> On Thu, Apr 26, 2001 at 05:54:22PM -0400, Igor Khavkine wrote:
>
> > > I had never anticipated anyone trying to implement pthreads for the Hurd
> > > in any way but by a substantial rewrite of the libc hurd code.
> >
> > When pthreads will actually be implemented. Do you think it would
> > be a good idea to rewrite the parts of glibc and hurd that use
> > cthreads now? It seems that there should be no reason to have two
> > competing thread implementations used in the same applications.
> >
> > Or is it too much work for little gain?
>
> The libc-hurd code seems to use the internal interfaces of the
> threading library, instead of the public interface. I haven't looked
> much at it beyond this yet, but if there's a strong requirement to do
> this, then it's not really possible to rewrite it before the threading
> interfaces are decided upon.
The pthread code of Mark uses the kernel routines to do the low level
stuff, the same as cthreads uses. Both pthreads and cthreads can
co-exists, as long as only one of them is used in an actual application.
The problem with the patch of Igor (IIRC) is that it does need some
clean-up. Also, the pthread stuff can't be seperated from glibc, as it
uses some hooks to do at-startup and at-fork initialization. I'm
building glibc now, but that's not going as fast as I had hoped.
Erik.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: Interaction of pthreads and cthreads,
Erik Verbruggen <=