From owner-freebsd-current@FreeBSD.ORG Sat Nov 11 06:56:40 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org 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 31C4716A47C; Sat, 11 Nov 2006 06:56:40 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C26543D5D; Sat, 11 Nov 2006 06:56:40 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id E36591A3C19; Fri, 10 Nov 2006 22:56:39 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0FE1851390; Sat, 11 Nov 2006 01:56:30 -0500 (EST) Date: Sat, 11 Nov 2006 01:56:29 -0500 From: Kris Kennaway To: Norikatsu Shigemura Message-ID: <20061111065629.GA82094@xor.obsecurity.org> References: <20061110151247.GA64530@zone3000.net> <20061111022044.8191e1c8.nork@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zhXaljGHf11kAtnf" Content-Disposition: inline In-Reply-To: <20061111022044.8191e1c8.nork@FreeBSD.org> User-Agent: Mutt/1.4.2.2i Cc: freebsd-current@FreeBSD.org Subject: Re: libpthread vs libthr. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 11 Nov 2006 06:56:40 -0000 --zhXaljGHf11kAtnf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 11, 2006 at 02:20:44AM +0900, Norikatsu Shigemura wrote: > On Fri, 10 Nov 2006 17:12:47 +0200 > Nikolay Pavlov wrote: > > Hi. In this post i am not trying to raise a discussion about teoretical > > advantages of some special threading model, but still i would like to > > figure out why libthr in it current state is not our default posix=20 > > thread library and could it be so in time of 7-STABLE? >=20 > I don't agree. Do test, run by again, do test. >=20 > I read a discussion about libpthread vs libthr, so I tested on > my environments(7-current SMP and 6-stable UP). My result is > NOT YET, and I resurrected to libpthread environment. >=20 > 1. libthr is not enough mature. > At this time, libpthread's pthread API support > libthr's > pthread API support. So libthr lacks of compatibility with > libpthread. It is not good. Which applications does this effect? I'm not aware of any (see below). > 2. Not PTHREAD_CFLAGS/PTHREAD_LIBS clean > At this time, tinderbox doesn't test PTHREAD_CFLAGS/ > PTHREAD_LIBS clean. We have need to check PTHREAD_CFLAGS/ > PTHREAD_LIBS clean on all ports. The existence of libmap makes this objection irrelevant. Also, sparc64 uses libthr by default and I'm not aware of any resulting port build problems. So apparently any missing API features are not widely used, or are successfully worked around. Can you provide evidence to the contrary? > 3. Is libthr environments useful? > I don't think. Yes, I think that some applications like mysql > are useful. However, in all FreeBSD environment system, by 1 > and 2, libthr is not useful. Maybe you don't care that libpthread's performance is terrible and e.g. this makes FreeBSD look bad on benchmarks, both published and when a user evaluates FreeBSD against other systems to decide whether or not to use it on their workloads - but surely most people do. Kris --zhXaljGHf11kAtnf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFVXQdWry0BWjoQKURAjUVAKDDMEQ/zS7hcgjw3loKuaENaddkggCfYyIs hDh0cZ6Ch1TXrebBNZKX36k= =IBWw -----END PGP SIGNATURE----- --zhXaljGHf11kAtnf--