From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 13:13:13 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 5C45237B401; Wed, 2 Apr 2003 13:13:13 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E37E43FAF; Wed, 2 Apr 2003 13:13:12 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0303.cvx22-bradley.dialup.earthlink.net ([209.179.199.48] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 190pXc-0006n4-00; Wed, 02 Apr 2003 13:13:05 -0800 Message-ID: <3E8B51FC.63F8BE55@mindspring.com> Date: Wed, 02 Apr 2003 13:11:24 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Sheldon Hearn References: <3E8B03E6.36871704@mindspring.com> <20030402154716.GE790@starjuice.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a456960d1adceca2a30f3deb1760084ef42601a10902912494350badd9bab72f9c350badd9bab72f9c cc: Alexander Leidinger cc: csujun@21cn.com cc: Robert Watson 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 21:13:13 -0000 Sheldon Hearn wrote: > On (2003/04/02 07:38), Terry Lambert wrote: > > 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? > > Dude, you should really try this stuff for yourself before naysaying > performance improvements on principle. It's actually quite impressive > for desktop users (at least). I have. I can't tell if it's the scheduler quantums or the concurrency from the threads. I'm going to have to specifically write code to find out, and it may take me a while to do it; I have to figure out a way to put the user space stalls back for descriptor accesses, so the tests run on an equal footing. Right now, I have to decide whether it's worth the hassle of combining the libc_r and libthr code to do that, or if I should just drop it, and let you guys turn FreeBSD's threads into Linux. PS: My gut tells me it's not the concurrency; the resolver is the bottleneck for things like Mozilla (IMO), and it still has to stall concurrency. PPS: I'll get back to you after I size the job, and decide. -- Terry