From owner-freebsd-current Tue Apr 13 15:52:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 1C10214E9B for ; Tue, 13 Apr 1999 15:52:08 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id SAA20531; Tue, 13 Apr 1999 18:49:14 -0400 (EDT) Date: Tue, 13 Apr 1999 18:49:14 -0400 (EDT) From: Daniel Eischen Message-Id: <199904132249.SAA20531@pcnet1.pcnet.com> To: eischen@vigrid.com, jdp@polstra.com Subject: Re: cvsup Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote: > > Does Modula-3 use libc_r, or does it have it's own user thread support? > > It has its own. It can be ported to use native threads, but it's a > non-negligible amount of work. It hardly seems worth it for the GUI > alone. No argmuent here. It's just that if it was using native threads, I would have been curious to see how CVSup worked before and after the recent changes to libc_r. But I guess I could have tested that myself :-) > My hunch is that it's not a fairness issue. It's just the fact that > when you block in disk I/O, the whole process (all threads) blocks. That statement made me think that Modula-3 had it's own threading support because our native threads using non-blocking file I/O. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message