From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 07:40:21 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 8122937B401; Wed, 2 Apr 2003 07:40:21 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE73F43FD7; Wed, 2 Apr 2003 07:40:18 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0051.cvx21-bradley.dialup.earthlink.net ([209.179.192.51] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190kLY-0002l4-00; Wed, 02 Apr 2003 07:40:18 -0800 Message-ID: <3E8B03E6.36871704@mindspring.com> Date: Wed, 02 Apr 2003 07:38:14 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Watson References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a488150adf550016d05c72c5c5a17c2e503ca473d225a0f487350badd9bab72f9c350badd9bab72f9c cc: Alexander Leidinger cc: csujun@21cn.com cc: current@freebsd.org cc: Jeff Roberson 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: Wed, 02 Apr 2003 15:40:21 -0000 Robert Watson wrote: > You should notice marked interactivity and UI latency improvements with > threaded GUI apps over libc_r because GUI threads will generally no longer > be blocked when disk I/O and blocking I/O occurs. For example, > applications like Open Office, Netscape, et al, really get a lot better > with 1:1. Likewise, non-interactive applications that are disk > I/O-intensive, such as mysql, will also perform substantially better > because a thread that hits blocking using an interface that doesn't > support non-blocking I/O (such as the file system) won't clog up the > application. Is the disk I/O really that big of an issue? All writes will be on underlying non-blocking descriptors; I guess you are saying that the interleaved I/O is more important, further down the system call interface than the top, and this becomes an issue? It seems to me that maybe the correct fix for this is to use AIO instead of non-blocking I/O, then? 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-). Has anyone tried compiling X11 to use libthr? Also, any ETA on the per process signal mask handing bug in libthr? Might not be safe to convert everything up front, in a rush of eager enthusiasm... -- Terry