From owner-freebsd-current Tue Apr 13 15:41: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 6F55D14C9C for ; Tue, 13 Apr 1999 15:40:59 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id PAA17991; Tue, 13 Apr 1999 15:38:39 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA75600; Tue, 13 Apr 1999 15:38:38 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199904132148.RAA13399@pcnet1.pcnet.com> Date: Tue, 13 Apr 1999 15:38:38 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Daniel Eischen Subject: Re: cvsup Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel Eischen 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. > The recent set of commits to libc_r changed the thread scheduling > mechanism to use ITIMER_PROF instead of ITIMER_VIRTUAL. This was > to allow for fairer scheduling with I/O bound threads. 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. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message