From owner-freebsd-hackers Tue Feb 27 9:24:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from a.mx.everquick.net (a.mx.everquick.net [216.89.137.3]) by hub.freebsd.org (Postfix) with ESMTP id A1A9E37B718 for ; Tue, 27 Feb 2001 09:24:09 -0800 (PST) (envelope-from eddy+public+spam@noc.everquick.net) Received: from localhost (eddy@localhost) by a.mx.everquick.net (8.9.0/8.8.7) with ESMTP id RAA19274 for ; Tue, 27 Feb 2001 17:24:09 GMT X-EverQuick-No-Abuse: Report any e-mail abuse to Date: Tue, 27 Feb 2001 17:24:09 +0000 (GMT) From: "E.B. Dreger" To: freebsd-hackers@freebsd.org Subject: Re: Where can I find out rules on blocking in threads? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Tue, 27 Feb 2001 15:15:33 +0000 (GMT) > From: E.B. Dreger > > Is this a library issue in libc_r? > > I just wrote a quick test program using rfork(RFMEM|RFPROC) to > create a child thread. Correction: RFTHREAD|RFPROC Sorry... I have RFMEM on the brain. The pseudocode gave the correct RFXXX flags. (I also typed "#if" instead of "#ifdef". FreeBSD multitasks better than I do this morning.) FWIW, does anyone know what Linuxthread's blocking behavior is? The original poster mentioned that Linux gave the desired behavior... what about the Linuxthreads library? Although I have written pthread applications, I prefer to do my thread programming at a lower level; hence my use of rfork(). Hopefully the info will be useful, though. Eddy --------------------------------------------------------------------------- Brotsman & Dreger, Inc. EverQuick Internet / EternalCommerce Division E-Mail: eddy@everquick.net Phone: (316) 794-8922 --------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message