Date: Thu, 28 Oct 1999 11:59:46 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: Jake Burkholder <jake@checker.org> Cc: Marcel Moolenaar <marcel@scc.nl>, freebsd-arch@freebsd.org Subject: Re: rfork patch, please comment Message-ID: <Pine.BSF.4.10.9910281156500.10856-100000@current1.whistle.com> In-Reply-To: <19991028181029.A85ED1FD7@io.yi.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I know I've been a fan of using rfork for native threads, (and all the support that we need for a linuxthreads is already there (see the linuxthread PORT to freebsd)). But I was speakin gwith terry the other day and he managed to convince me that there is an even better way that we could do this. It's really quite elegant. On Thu, 28 Oct 1999, Jake Burkholder wrote: > > [No time yet to dig into this in more detail] > > > > Jake Burkholder wrote: > > > > > I've made a patch that adds linux 'clone' style support > > > to rfork, and I'd like to hear opinions on whether this > > > is an ok way to do it. > > > > Does this improve the support for clone in the Linuxulator? > > No, there is already some support there. That's where I got the idea, > see /usr/src/sys/i386/linux/linux_misc.c:linux_clone. > > What it does, as I see it, is open the door for native kernel > threads, which of course still requires a thread-safe libc. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-arch" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9910281156500.10856-100000>