From owner-freebsd-arch@FreeBSD.ORG Tue Oct 25 13:06:18 2005 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B4E9016A41F; Tue, 25 Oct 2005 13:06:16 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <435E2DCF.6080809@freebsd.org> Date: Tue, 25 Oct 2005 21:06:23 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <20051025120538.K52058@fledge.watson.org> In-Reply-To: <20051025120538.K52058@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Daniel Eischen , arch@freebsd.org Subject: Re: libc_r is deprecated X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Oct 2005 13:06:18 -0000 Robert Watson wrote: > > On Mon, 24 Oct 2005, Daniel Eischen wrote: > >> On Tue, 25 Oct 2005, David Xu wrote: >> >>> Folks, >>> >>> For years development, we now have libpthread and libthr, libc_r >>> does not support SMP or multi-core processor, also it has many bugs >>> (still in our bug database), also threads@ developers seems not have >>> interest to maintain it, it is doomed, so I would like to disconnect >>> it from buildworld, and sometimes later, I would like to remove it. >> >> >> Deprecate in 6.x and remove in 7.0? >> >> Someone might be able to make a port out of it also. > > > I'd like to keep it around in some form -- I recently ran a series of > HTTP-related benchmarks and libc_r benchmarked signicantly faster than > other libraries on both UP and SMP. I'm working to refine the > benchmark for improved realism, and will see if that persists. > However, when it comes to understanding scheduling and threading > behavior, I think libc_r remains useful... > > Robert N M Watson > libc_r runs on single kernel thread, so if you are continue using libc_r, you are not testing TCP/IP with multithreads program, this may give you false data. Only kernel threads based server can test to see if the TCP/IP stack locking works well. David Xu