From owner-freebsd-current Wed Nov 18 16:13:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07870 for freebsd-current-outgoing; Wed, 18 Nov 1998 16:13:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07865 for ; Wed, 18 Nov 1998 16:13:20 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id SAA66500; Wed, 18 Nov 1998 18:12:47 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199811190012.SAA66500@ns.tar.com> From: "Richard Seaman, Jr." To: "HighWind Software Information" Cc: "current@FreeBSD.ORG" , "green@unixhelp.org" Date: Wed, 18 Nov 98 18:12:47 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: LinuxThreads (was Re: RFSIGSHARE ready?) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998 17:52:17 -0500 (EST), HighWind Software Information wrote: > >I have a question with regard to LinuxThreads on FreeBSD 3.0 > >Is this a substitute for libc_r?? > >How does this fit into the picture? > >-Rob It is my impression, though I can't speak for him, that Brian Feldman was working on getting linuxthreads working in linux emulation. One clear benefit would be, if it works, that linux apps compiled against linuxthreads would run on FreeBSD using the linux emulation. I guess that if you can figure out how to link your app to the linux threads and glibc libraries, your "native" FreeBSD app could run linux threads too. I've also been playing around with a "port" of linuxthreads to FreeBSD that wouldn't need the linux shared libraries or linux emulation, and would link to native FreeBSD apps, and use the FreeBSD libc library. I wouldn't call it a substitute for libc_r, but rather an alternative. I recently asked how much interest there was in a "kernel" pthreads implementation that would be a "one-to-one" mapping of threads to kernel schedulable entities. There were 2 positive responses, and lots of responses about how FreeBSD should use various alternative "models". With the work Brian started on signal sharing (which would be necessary for almost any kind of "kernel threads" implementation, at least in varying degrees) I thought I would see how hard a linuxthreads port would be. My theory was that it might be a "quick fix" for kernel threads under FreeBSD, while everyone works on their more sophisticated kernel threads models. There are some libc issues to be worked out (which would have to be worked out for almost any "kernel threads" model), but if anyone is interested, I think linuxthreads can work. However, I haven't seen much interest in a "one-to-one" kernel threads implemenation, so I've just been poking around quietly on the subject. I'd be happy to tar up the "port" and send it to anyone who wants to play around with it, or to post it somewhere. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message