From owner-freebsd-current@FreeBSD.ORG Thu Apr 10 08:53:18 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7BEA37B401; Thu, 10 Apr 2003 08:53:18 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id E59A643F85; Thu, 10 Apr 2003 08:53:17 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (localhost [127.0.0.1]) by haldjas.folklore.ee (8.12.3/8.11.3) with ESMTP id h3AFrGUE074447; Thu, 10 Apr 2003 18:53:16 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost)h3AFrGEd074444; Thu, 10 Apr 2003 18:53:16 +0300 (EEST) Date: Thu, 10 Apr 2003 18:53:16 +0300 (EEST) From: Narvi To: Robert Watson In-Reply-To: Message-ID: <20030410183206.X61076-100000@haldjas.folklore.ee> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: libthr and 1:1 threading. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 15:53:19 -0000 On Wed, 2 Apr 2003, Robert Watson wrote: > > The GUI thread issues are something I hadn't considered; I don't > > generally think of user space CPU intensive operations like that, but I > > guess it has to be rendered some time. 8-). > > One of the problems I've run into is where you lose interactivity during > file saves and other disk-intensive operations in OpenOffice. Other > windows could in theory still be processing UI events, such as menu > clicks, etc, but since you're dumping several megabytes of data to disk or > doing interactive file operations that require waiting on disk latency, > you end up with a fairly nasty user experience. One way to explore this > effect is to do a side-by-side comparison of the behavior of OpenOffice > and Mozilla linked against libc_r and linuxthreads. I haven't actually > instrumented the kernel, but it might be quite interesting to do > so--attempt to estimate the total impact of disk stalls on libc_r. From a > purely qualitivative perspective, there is quite a noticeable difference. > Actually, if you went in and did a bunch of SMPng style rework on Openoffice threading it probably would be more true than right now as you easily run into 'giant lock' style problems. Mozilla would probably be a better example. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Network Associates Laboratories >