From owner-freebsd-current Wed Apr 14 21:24:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 9A5C615016 for ; Wed, 14 Apr 1999 21:24:41 -0700 (PDT) (envelope-from gjp@noop.colo.erols.net) Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net) by noop.colo.erols.net with esmtp (Exim 2.12 #1) id 10XdfU-000A1H-00; Thu, 15 Apr 1999 00:22:24 -0400 To: Thomas Schuerger Cc: mi@aldan.algebra.com, jdp@polstra.com, current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: cvsup In-reply-to: Your message of "Tue, 13 Apr 1999 21:23:30 +0200." <199904131923.VAA21668@wurzelausix.cs.uni-sb.de> Date: Thu, 15 Apr 1999 00:22:23 -0400 Message-ID: <38518.924150143@noop.colo.erols.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas Schuerger wrote in message ID <199904131923.VAA21668@wurzelausix.cs.uni-sb.de>: > cvsup is mostly based on disk (and network) I/O, so there shouldn't > be a problem with properly updating the GUI. Someone said it is > done in a separate process, so I still wonder why the GUI is updated > so slowly on my PII/450. My bet is that when cvsup blocks on network or disk i/o, the process is blocked (since we don't have kernel support for thread scheduling), so the display update gets blocked as well... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message