From owner-freebsd-threads@FreeBSD.ORG Mon Sep 24 11:08:41 2007 Return-Path: Delivered-To: freebsd-threads@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB4A716A4CE for ; Mon, 24 Sep 2007 11:08:41 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A3DD913C48D for ; Mon, 24 Sep 2007 11:08:41 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l8OB8f69064344 for ; Mon, 24 Sep 2007 11:08:41 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l8OB8ebD064340 for freebsd-threads@FreeBSD.org; Mon, 24 Sep 2007 11:08:40 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Sep 2007 11:08:40 GMT Message-Id: <200709241108.l8OB8ebD064340@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-threads@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 11:08:41 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s threa/76690 threads fork hang in child for -lc_r 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/20016 threads pthreads: Cannot set scheduling timer/Cannot set virtu s threa/24472 threads libc_r does not honor SO_SNDTIMEO/SO_RCVTIMEO socket o s threa/24632 threads libc_r delicate deviation from libc in handling SIGCHL s bin/32295 threads pthread dont dequeue signals s threa/34536 threads accept() blocks other threads o kern/38549 threads the procces compiled whith pthread stopped in pthread_ s threa/39922 threads [threads] [patch] Threaded applications executed with s threa/48856 threads Setting SIGCHLD to SIG_IGN still leaves zombies under s threa/49087 threads Signals lost in programs linked with libc_r s kern/64313 threads FreeBSD (OpenBSD) pthread implicit set/unset O_NONBLOC o threa/70975 threads unexpected and unreliable behaviour when using SYSV se o threa/72429 threads threads blocked in stdio (fgets, etc) are not cancella o threa/72953 threads fork() unblocks blocked signals w/o PTHREAD_SCOPE_SYST o threa/75273 threads FBSD 5.3 libpthread (KSE) bug o threa/75374 threads pthread_kill() ignores SA_SIGINFO flag s threa/76694 threads fork cause hang in dup()/close() function in child (-l o threa/79683 threads svctcp_create() fails if multiple threads call at the o threa/80435 threads panic on high loads o threa/83914 threads [libc] popen() doesn't work in static threaded program s threa/84483 threads problems with devel/nspr and -lc_r on 4.x o threa/85160 threads [libthr] [patch] libobjc + libpthread/libthr crash pro o kern/91266 threads [threads] Trying sleep, but thread marked as sleeping s threa/94467 threads send(), sendto() and sendmsg() are not correct in libc s threa/100815 threads FBSD 5.5 broke nanosleep in libc_r o threa/101323 threads fork(2) in threaded programs broken. o threa/103975 threads Implicit loading/unloading of libpthread.so may crash o threa/110636 threads gdb(1): using gdb with multi thread application with l o threa/113666 threads misc/shared-mime-info doesn't install, can't find thre 28 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- s kern/19247 threads uthread_sigaction.c does not do anything wrt SA_NOCLDW s kern/22190 threads A threaded read(2) from a socketpair(2) fd can sometim s threa/30464 threads pthread mutex attributes -- pshared s threa/37676 threads libc_r: msgsnd(), msgrcv(), pread(), pwrite() need wra s threa/40671 threads pthread_cancel doesn't remove thread from condition qu s threa/69020 threads pthreads library leaks _gc_mutex o threa/79887 threads [patch] freopen() isn't thread-safe o threa/80992 threads abort() sometimes not caught by gdb depending on threa o threa/81534 threads [libc_r] [patch] libc_r close() will fail on any fd ty o threa/110306 threads apache 2.0 segmentation violation when calling gethost o threa/115211 threads pthread_atfork misbehaves in initial thread 11 problems total. From owner-freebsd-threads@FreeBSD.ORG Mon Sep 24 18:00:41 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACF6716A420 for ; Mon, 24 Sep 2007 18:00:41 +0000 (UTC) (envelope-from lavajoe@gentoo.org) Received: from shadow.wildlava.net (shadow.wildlava.net [67.40.138.81]) by mx1.freebsd.org (Postfix) with ESMTP id 7CDD213C47E for ; Mon, 24 Sep 2007 18:00:41 +0000 (UTC) (envelope-from lavajoe@gentoo.org) Received: from [67.40.138.82] (crater.wildlava.net [67.40.138.82]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shadow.wildlava.net (Postfix) with ESMTP id B7D7A8F431 for ; Mon, 24 Sep 2007 12:00:40 -0600 (MDT) Message-ID: <46F7FB47.5060005@gentoo.org> Date: Mon, 24 Sep 2007 12:00:39 -0600 From: Joe Peterson User-Agent: Thunderbird 2.0.0.6 (X11/20070822) MIME-Version: 1.0 To: freebsd-threads@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: How will libpthread, libthr, etc. be linked in 7.0? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 18:00:41 -0000 Hi all, I'm still working on my libpthread/libthr "symbol mixing" issue that caused the %%gs register to get clobbered. If you recall, it seems that the libmap.conf mechanism does not completely prevent symbols in the old libpthread.so from being used along with libthr.so symbols - i.e. a big problem. Anyway, for my gentoo/FreeBSD 6.2 system, I am experimenting with symlinking the libs for a more sure way to prevent the problem, and it's working great so far. No crashes and no other problems so far. Also, I found this post: http://lists.freebsd.org/pipermail/freebsd-threads/2007-May/003930.html which talks about what is being done in 7.0. Looks like similar symlinking is either now being done or is being considered. Can anyone here give a status on what is linked to what in 7.0? If the following: /usr/lib/libpthread.a -> libthr.a /usr/lib/libpthread.so -> libthr.so /usr/lib/libpthread_p.a -> libthr_p.a is being done, then this would be similar to what I am doing now on my 6.2 system. BTW, I am also linking libc_r.so to libthr.so, which may or may not be overkill. The issue I saw seemed libpthread-specific, but for safety's sake, I went this one step further. If anyone has any thoughts on this, let me know. Thanks! Joe From owner-freebsd-threads@FreeBSD.ORG Mon Sep 24 18:13:05 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A234F16A41B for ; Mon, 24 Sep 2007 18:13:05 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 7658913C46E for ; Mon, 24 Sep 2007 18:13:05 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.1/8.14.1/NETPLEX) with ESMTP id l8OID3oL026334; Mon, 24 Sep 2007 14:13:03 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.netplex.net [204.213.176.10]); Mon, 24 Sep 2007 14:13:03 -0400 (EDT) Date: Mon, 24 Sep 2007 14:13:03 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Joe Peterson In-Reply-To: <46F7FB47.5060005@gentoo.org> Message-ID: References: <46F7FB47.5060005@gentoo.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-threads@freebsd.org Subject: Re: How will libpthread, libthr, etc. be linked in 7.0? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 18:13:05 -0000 On Mon, 24 Sep 2007, Joe Peterson wrote: > Hi all, > > I'm still working on my libpthread/libthr "symbol mixing" issue that > caused the %%gs register to get clobbered. If you recall, it seems that > the libmap.conf mechanism does not completely prevent symbols in the old > libpthread.so from being used along with libthr.so symbols - i.e. a big > problem. So file a bug report (or fix it) on rtld-elf. If libmapping isn't working correctly, then the problem should be fixed, not glossed over. Regardless of the links, someone may want to use libmap.conf to map libthr to libkse or some other library mapping similarly. -- DE From owner-freebsd-threads@FreeBSD.ORG Mon Sep 24 20:19:52 2007 Return-Path: Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A492716A419; Mon, 24 Sep 2007 20:19:52 +0000 (UTC) (envelope-from emaste@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7DCEB13C457; Mon, 24 Sep 2007 20:19:52 +0000 (UTC) (envelope-from emaste@FreeBSD.org) Received: from freefall.freebsd.org (emaste@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l8OKJq3m098659; Mon, 24 Sep 2007 20:19:52 GMT (envelope-from emaste@freefall.freebsd.org) Received: (from emaste@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l8OKJqrM098655; Mon, 24 Sep 2007 20:19:52 GMT (envelope-from emaste) Date: Mon, 24 Sep 2007 20:19:52 GMT Message-Id: <200709242019.l8OKJqrM098655@freefall.freebsd.org> To: emaste@phaedrus.sandvine.ca, emaste@FreeBSD.org, freebsd-threads@FreeBSD.org, emaste@FreeBSD.org From: emaste@FreeBSD.org Cc: Subject: Re: threads/81534: [libc_r] [patch] libc_r close() will fail on any fd type that doesn't support fstat() X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 20:19:52 -0000 Synopsis: [libc_r] [patch] libc_r close() will fail on any fd type that doesn't support fstat() State-Changed-From-To: open->closed State-Changed-By: emaste State-Changed-When: Mon Sep 24 20:18:14 UTC 2007 State-Changed-Why: libc_r is deprecated post 4.x. Not worth addressing this. Responsible-Changed-From-To: freebsd-threads->emaste Responsible-Changed-By: emaste Responsible-Changed-When: Mon Sep 24 20:18:14 UTC 2007 Responsible-Changed-Why: Grab to close. http://www.freebsd.org/cgi/query-pr.cgi?pr=81534 From owner-freebsd-threads@FreeBSD.ORG Mon Sep 24 21:33:30 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D492516A481 for ; Mon, 24 Sep 2007 21:33:30 +0000 (UTC) (envelope-from lavajoe@gentoo.org) Received: from shadow.wildlava.net (shadow.wildlava.net [67.40.138.81]) by mx1.freebsd.org (Postfix) with ESMTP id 9EEE113C4B2 for ; Mon, 24 Sep 2007 21:33:30 +0000 (UTC) (envelope-from lavajoe@gentoo.org) Received: from [10.1.2.160] (pawnee.wildlava.net [67.40.138.85]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by shadow.wildlava.net (Postfix) with ESMTP id BC8DF8F44A; Mon, 24 Sep 2007 15:33:29 -0600 (MDT) Message-ID: <46F82D06.2090806@gentoo.org> Date: Mon, 24 Sep 2007 15:32:54 -0600 From: Joe Peterson User-Agent: Thunderbird 2.0.0.6 (X11/20070816) MIME-Version: 1.0 To: Daniel Eischen References: <46F7FB47.5060005@gentoo.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-threads@freebsd.org Subject: Re: How will libpthread, libthr, etc. be linked in 7.0? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 21:33:30 -0000 I agree, and we are still looking into it. Unfortunately, I may need some help, since we hit somewhat of a dead end on figuring out what is really happening (I am not familiar with the inner workings of rtld-elf). But I am still interested in what's planned for 7.0 in terms of the symlinks on the threading libs in /usr/lib. Can you fill me in on this? Also, is libc_r completely missing from 7.0 by now? Thanks, Joe Daniel Eischen wrote: > On Mon, 24 Sep 2007, Joe Peterson wrote: > >> Hi all, >> >> I'm still working on my libpthread/libthr "symbol mixing" issue that >> caused the %%gs register to get clobbered. If you recall, it seems that >> the libmap.conf mechanism does not completely prevent symbols in the old >> libpthread.so from being used along with libthr.so symbols - i.e. a big >> problem. > > So file a bug report (or fix it) on rtld-elf. If libmapping > isn't working correctly, then the problem should be fixed, > not glossed over. Regardless of the links, someone may > want to use libmap.conf to map libthr to libkse or some > other library mapping similarly. > From owner-freebsd-threads@FreeBSD.ORG Mon Sep 24 21:45:03 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E31016A417 for ; Mon, 24 Sep 2007 21:45:03 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id E327E13C4B5 for ; Mon, 24 Sep 2007 21:45:02 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.1/8.14.1/NETPLEX) with ESMTP id l8OLj1eH012579; Mon, 24 Sep 2007 17:45:01 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.netplex.net [204.213.176.10]); Mon, 24 Sep 2007 17:45:01 -0400 (EDT) Date: Mon, 24 Sep 2007 17:45:01 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Joe Peterson In-Reply-To: <46F82D06.2090806@gentoo.org> Message-ID: References: <46F7FB47.5060005@gentoo.org> <46F82D06.2090806@gentoo.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-threads@freebsd.org Subject: Re: How will libpthread, libthr, etc. be linked in 7.0? X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 21:45:03 -0000 On Mon, 24 Sep 2007, Joe Peterson wrote: > I agree, and we are still looking into it. Unfortunately, I may need > some help, since we hit somewhat of a dead end on figuring out what is > really happening (I am not familiar with the inner workings of rtld-elf). > > But I am still interested in what's planned for 7.0 in terms of the > symlinks on the threading libs in /usr/lib. Can you fill me in on this? > Also, is libc_r completely missing from 7.0 by now? This is already discussed in the archives, committed in the src tree, etc. If you want, install a -current system and see for yourself ;-) -- DE From owner-freebsd-threads@FreeBSD.ORG Tue Sep 25 21:15:38 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B060816A41B for ; Tue, 25 Sep 2007 21:15:38 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 7DD7113C45B for ; Tue, 25 Sep 2007 21:15:38 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id l8PKp8Cw044587 for ; Tue, 25 Sep 2007 13:51:08 -0700 (PDT) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.1/8.14.1/Submit) id l8PKp8tB044586 for freebsd-threads@freebsd.org; Tue, 25 Sep 2007 13:51:08 -0700 (PDT) (envelope-from obrien) Date: Tue, 25 Sep 2007 13:51:08 -0700 From: "David O'Brien" To: freebsd-threads@freebsd.org Message-ID: <20070925205108.GA44536@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.16 (2007-06-09) Subject: libc_r in 7.0 source tree X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 21:15:38 -0000 Hi folks, Seems we still have src/lib/libc_r in what is to be 7.0-RELEASE. libc_r has been 100% disconnected from the build for a year now: RCS file: /home/ncvs/src/lib/Makefile,v revision 1.218 date: 2006/09/30 11:32:46; author: ru; state: Exp; lines: +1 -6 Removed libc_r build support. with no knob to enable building it. I have a patch to propose cvs rm'ing it for 7.0 release. So please speak now if there's a good reason not to do this. thanks, -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? Let's not play "Jeopardy-style quoting" From owner-freebsd-threads@FreeBSD.ORG Tue Sep 25 22:46:53 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CE7816A41B for ; Tue, 25 Sep 2007 22:46:53 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id B06EE13C44B for ; Tue, 25 Sep 2007 22:46:52 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id 0389EEB7A8A; Wed, 26 Sep 2007 06:31:38 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id 231BSS9sWEFW; Wed, 26 Sep 2007 06:31:26 +0800 (CST) Received: from LI-Xins-MacBook.local (71.5.7.139.ptr.us.xo.net [71.5.7.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 24F0CEB79B0; Wed, 26 Sep 2007 06:31:25 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type; b=oJNoF/OKXV5UajcIeWvH9camKzsWDaYHeASmumOxLMgfuqbq7E0ceh4y5sUcP7Cgf mA3m8JDG4DLn2TNdBPnJQ== Message-ID: <46F98C1F.70407@delphij.net> Date: Tue, 25 Sep 2007 15:30:55 -0700 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: obrien@freebsd.org References: <20070925205108.GA44536@dragon.NUXI.org> In-Reply-To: <20070925205108.GA44536@dragon.NUXI.org> X-Enigmail-Version: 0.95.3 OpenPGP: url=http://www.delphij.net/delphij.asc Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig926235EDCF40C2D0C7CE3634" Cc: freebsd-threads@freebsd.org Subject: Re: libc_r in 7.0 source tree X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 22:46:53 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig926235EDCF40C2D0C7CE3634 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable David O'Brien wrote: > Hi folks, > Seems we still have src/lib/libc_r in what is to be 7.0-RELEASE. > libc_r has been 100% disconnected from the build for a year now: >=20 > RCS file: /home/ncvs/src/lib/Makefile,v > revision 1.218 > date: 2006/09/30 11:32:46; author: ru; state: Exp; lines: +1 -6 > Removed libc_r build support. >=20 > with no knob to enable building it. I have a patch to propose cvs rm'i= ng > it for 7.0 release. So please speak now if there's a good reason not t= o > do this. I think the initial discussion was that libc_r should be kept as a reference for thread library implementation. Perhaps it's time to have it in ports/? :-) Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enig926235EDCF40C2D0C7CE3634 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+YwfOfuToMruuMARCjy3AJwJ1NBW3x36x/dub8dv/qGExXf4ZgCgijwy wGKMC8NhH8KWeHY6MOm3bg8= =phPu -----END PGP SIGNATURE----- --------------enig926235EDCF40C2D0C7CE3634-- From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 00:20:39 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 551DF16A479 for ; Wed, 26 Sep 2007 00:20:39 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 1D90913C4AA for ; Wed, 26 Sep 2007 00:20:38 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id l8Q0KcvL056156 for ; Tue, 25 Sep 2007 17:20:38 -0700 (PDT) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.1/8.14.1/Submit) id l8Q0KcmA056155 for freebsd-threads@freebsd.org; Tue, 25 Sep 2007 17:20:38 -0700 (PDT) (envelope-from obrien) Date: Tue, 25 Sep 2007 17:20:38 -0700 From: "David O'Brien" To: freebsd-threads@freebsd.org Message-ID: <20070926002038.GA56119@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.16 (2007-06-09) Subject: Renaming our threads libs X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 00:20:39 -0000 We have little time before 7.0-RELEASE to get this right.. For consistency and expectations from users (especially of other OS's), should we ask RE@ to rename libpthread to libkse (or whatever) and rename libthr to libpthread? Remember - what we release 7.0 will be burned into folks Makefile's and vernacular. -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? Let's not play "Jeopardy-style quoting" From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 00:27:36 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E037616A418; Wed, 26 Sep 2007 00:27:36 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id 8039713C474; Wed, 26 Sep 2007 00:27:36 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id 80AD1EB9E06; Wed, 26 Sep 2007 08:28:01 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id C+7d-3JN0FXv; Wed, 26 Sep 2007 08:27:48 +0800 (CST) Received: from LI-Xins-MacBook.local (71.5.7.139.ptr.us.xo.net [71.5.7.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 4A283EB11EA; Wed, 26 Sep 2007 08:27:48 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type; b=TsYHN6LWoQuGrGp//NVAjsZEYRZbJKyFjBqgZtvag4TtcHWsvLidtDnjcwIZqG8XG Tz45GTMjk/JOYwjP7lGJA== Message-ID: <46F9A764.6000008@delphij.net> Date: Tue, 25 Sep 2007 17:27:16 -0700 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: obrien@freebsd.org References: <20070926002038.GA56119@dragon.NUXI.org> In-Reply-To: <20070926002038.GA56119@dragon.NUXI.org> X-Enigmail-Version: 0.95.3 OpenPGP: url=http://www.delphij.net/delphij.asc Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig9366D0C793F64D24CF6C6DE1" Cc: freebsd-threads@freebsd.org Subject: Re: Renaming our threads libs X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 00:27:37 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9366D0C793F64D24CF6C6DE1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable David O'Brien wrote: > We have little time before 7.0-RELEASE to get this right.. >=20 > For consistency and expectations from users (especially of other OS's),= > should we ask RE@ to rename libpthread to libkse (or whatever) and rena= me > libthr to libpthread? Remember - what we release 7.0 will be burned in= to > folks Makefile's and vernacular. Do you mean repocopy from src/lib/libpthread -> src/lib/libkse? Because libpthread.so.X is now installed as a symbolic link to actual default threading library I think it would be an overkill to rename libthr to libpthread, but to reduce confusion it might be better to rename lib/libpthread to lib/libkse. Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enig9366D0C793F64D24CF6C6DE1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG+adlOfuToMruuMARCqrvAJ9Zp4eP+81IOzl/eY5wHueGR22i0QCfXwKI r2Yqq8s1rqvosTsEJxdeH8Y= =fih0 -----END PGP SIGNATURE----- --------------enig9366D0C793F64D24CF6C6DE1-- From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 00:38:56 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB35E16A419 for ; Wed, 26 Sep 2007 00:38:56 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 8917B13C474 for ; Wed, 26 Sep 2007 00:38:56 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id l8Q0cnWZ057205; Tue, 25 Sep 2007 17:38:49 -0700 (PDT) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.1/8.14.1/Submit) id l8Q0cmQT057204; Tue, 25 Sep 2007 17:38:48 -0700 (PDT) (envelope-from obrien) Date: Tue, 25 Sep 2007 17:38:48 -0700 From: "David O'Brien" To: d@delphij.net Message-ID: <20070926003848.GA56318@dragon.NUXI.org> References: <20070926002038.GA56119@dragon.NUXI.org> <46F9A764.6000008@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46F9A764.6000008@delphij.net> X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-threads@freebsd.org Subject: Re: Renaming our threads libs X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 00:38:56 -0000 On Tue, Sep 25, 2007 at 05:27:16PM -0700, LI Xin wrote: > David O'Brien wrote: > > We have little time before 7.0-RELEASE to get this right.. > > > > For consistency and expectations from users (especially of other OS's), > > should we ask RE@ to rename libpthread to libkse (or whatever) and rename > > libthr to libpthread? Remember - what we release 7.0 will be burned into > > folks Makefile's and vernacular. > > Do you mean repocopy from src/lib/libpthread -> src/lib/libkse? Because > libpthread.so.X is now installed as a symbolic link to actual default > threading library I think it would be an overkill to rename libthr to > libpthread, I think it is most clear when the name of the object someone wants (in this case they call by the name libpthread) lives in src/lib/libpthread. We've done a pretty good job in the BSD code tree of keeping things clean like this. Don't want to loose what I see as some of the value of BSD developing. Also renaming libthr to libpthread reduces confusion in say the output of 'ldd /usr/bin/csup'. > but to reduce confusion it might be better to rename > lib/libpthread to lib/libkse. Yes that at a mininum. -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? Let's not play "Jeopardy-style quoting" From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 00:39:17 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7EF1116A41B; Wed, 26 Sep 2007 00:39:17 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 2FB3413C467; Wed, 26 Sep 2007 00:39:17 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.1/8.14.1/NETPLEX) with ESMTP id l8Q0d9gm012730; Tue, 25 Sep 2007 20:39:09 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.netplex.net [204.213.176.10]); Tue, 25 Sep 2007 20:39:09 -0400 (EDT) Date: Tue, 25 Sep 2007 20:39:09 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: d@delphij.net In-Reply-To: <46F9A764.6000008@delphij.net> Message-ID: References: <20070926002038.GA56119@dragon.NUXI.org> <46F9A764.6000008@delphij.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: obrien@freebsd.org, freebsd-threads@freebsd.org Subject: Re: Renaming our threads libs X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 00:39:17 -0000 On Tue, 25 Sep 2007, LI Xin wrote: > David O'Brien wrote: >> We have little time before 7.0-RELEASE to get this right.. >> >> For consistency and expectations from users (especially of other OS's), >> should we ask RE@ to rename libpthread to libkse (or whatever) and rename >> libthr to libpthread? Remember - what we release 7.0 will be burned into >> folks Makefile's and vernacular. > > Do you mean repocopy from src/lib/libpthread -> src/lib/libkse? Because > libpthread.so.X is now installed as a symbolic link to actual default > threading library I think it would be an overkill to rename libthr to > libpthread, but to reduce confusion it might be better to rename > lib/libpthread to lib/libkse. I think it's fine just the way it is. Everyone currently knows libpthread and libthr by name. libpthread is currently installed as libkse. I don't think you need to repo copy the src tree to match, unless there is too much heartburn over having the src directory named differently from the library. I think libthr should remain named as it currently is. The links are a convenient way to swap between either of the two (or future) libraries as default and still leave a visible sign as to which library is the default. So I really think those should stay as they are. -- DE From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 00:44:26 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3422C16A417; Wed, 26 Sep 2007 00:44:26 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 0E66013C448; Wed, 26 Sep 2007 00:44:25 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 0391F1A4D90; Tue, 25 Sep 2007 17:44:26 -0700 (PDT) Date: Tue, 25 Sep 2007 17:44:25 -0700 From: Alfred Perlstein To: Daniel Eischen Message-ID: <20070926004425.GF37370@elvis.mu.org> References: <20070926002038.GA56119@dragon.NUXI.org> <46F9A764.6000008@delphij.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: d@delphij.net, obrien@freebsd.org, freebsd-threads@freebsd.org Subject: Re: Renaming our threads libs X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 00:44:26 -0000 * Daniel Eischen [070925 17:39] wrote: > On Tue, 25 Sep 2007, LI Xin wrote: > > >David O'Brien wrote: > >>We have little time before 7.0-RELEASE to get this right.. > >> > >>For consistency and expectations from users (especially of other OS's), > >>should we ask RE@ to rename libpthread to libkse (or whatever) and rename > >>libthr to libpthread? Remember - what we release 7.0 will be burned into > >>folks Makefile's and vernacular. > > > >Do you mean repocopy from src/lib/libpthread -> src/lib/libkse? Because > >libpthread.so.X is now installed as a symbolic link to actual default > >threading library I think it would be an overkill to rename libthr to > >libpthread, but to reduce confusion it might be better to rename > >lib/libpthread to lib/libkse. > > I think it's fine just the way it is. Everyone currently knows > libpthread and libthr by name. libpthread is currently installed > as libkse. I don't think you need to repo copy the src tree > to match, unless there is too much heartburn over having the > src directory named differently from the library. I think > libthr should remain named as it currently is. > > The links are a convenient way to swap between either of > the two (or future) libraries as default and still leave a > visible sign as to which library is the default. So I > really think those should stay as they are. The current situation only makes sense to those that have been watching the deal from day one, in "user land" confusion reigns and we're punishing those that choose our platform but letting it continue. you should see the threads I've seen at multiple places, it's not even 100% clear to me what I should be pushing as the "supported" threading platform these days. -- - Alfred Perlstein From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 00:49:45 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8410C16A418 for ; Wed, 26 Sep 2007 00:49:45 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 6332913C455 for ; Wed, 26 Sep 2007 00:49:45 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 6C22E1A4D7C; Tue, 25 Sep 2007 17:23:41 -0700 (PDT) Date: Tue, 25 Sep 2007 17:23:41 -0700 From: Alfred Perlstein To: David O'Brien Message-ID: <20070926002341.GE37370@elvis.mu.org> References: <20070926002038.GA56119@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070926002038.GA56119@dragon.NUXI.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-threads@freebsd.org Subject: Re: Renaming our threads libs X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 00:49:45 -0000 * David O'Brien [070925 17:20] wrote: > We have little time before 7.0-RELEASE to get this right.. > > For consistency and expectations from users (especially of other OS's), > should we ask RE@ to rename libpthread to libkse (or whatever) and rename > libthr to libpthread? Remember - what we release 7.0 will be burned into > folks Makefile's and vernacular. Could we rename libpthread(kse) -> /dev/null? :D Or is it being worked on? -Alfred > > -- > -- David (obrien@FreeBSD.org) > Q: Because it reverses the logical flow of conversation. > A: Why is top-posting (putting a reply at the top of the message) frowned upon? > Let's not play "Jeopardy-style quoting" > _______________________________________________ > freebsd-threads@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-threads > To unsubscribe, send any mail to "freebsd-threads-unsubscribe@freebsd.org" -- - Alfred Perlstein From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 00:53:13 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44E1316A41B; Wed, 26 Sep 2007 00:53:13 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id E78AE13C461; Wed, 26 Sep 2007 00:53:12 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.1/8.14.1/NETPLEX) with ESMTP id l8Q0r7lb019031; Tue, 25 Sep 2007 20:53:07 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.netplex.net [204.213.176.10]); Tue, 25 Sep 2007 20:53:07 -0400 (EDT) Date: Tue, 25 Sep 2007 20:53:07 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Alfred Perlstein In-Reply-To: <20070926004425.GF37370@elvis.mu.org> Message-ID: References: <20070926002038.GA56119@dragon.NUXI.org> <46F9A764.6000008@delphij.net> <20070926004425.GF37370@elvis.mu.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: d@delphij.net, obrien@freebsd.org, freebsd-threads@freebsd.org Subject: Re: Renaming our threads libs X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 00:53:13 -0000 On Tue, 25 Sep 2007, Alfred Perlstein wrote: > > The current situation only makes sense to those that have been > watching the deal from day one, in "user land" confusion reigns > and we're punishing those that choose our platform but letting > it continue. And when someone has a threading bug, how are we suppose to know which thread library it is in? A simple 'ldd application' works if the thread libraries stay named differently. And a simple 'ls -l /lib/libpthread*' also works easily. I don't see how installing either libthr or libkse as libpthread is going to help. It's not clear which one is "libpthread" that way. The links make it clear, as well as 'ldd' output. And this can only help us when there are problem reports submitted. I really don't see how there is a big confusion. All ports should use -lpthread or -pthread, as well as other 3rd party applications. If someone is smart enough and wants to bypass the default threading library, then they are going to be less confused by always having the libraries consistently named regardless of what DEFAULT_THREAD_LIB is set to. -- DE From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 00:55:40 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6263616A421 for ; Wed, 26 Sep 2007 00:55:40 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outZ.internet-mail-service.net (outZ.internet-mail-service.net [216.240.47.249]) by mx1.freebsd.org (Postfix) with ESMTP id 25BC913C447 for ; Wed, 26 Sep 2007 00:55:40 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Tue, 25 Sep 2007 17:42:22 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id AF9181264F6; Tue, 25 Sep 2007 17:42:21 -0700 (PDT) Message-ID: <46F9AAEC.7050808@elischer.org> Date: Tue, 25 Sep 2007 17:42:20 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Daniel Eischen References: <20070926002038.GA56119@dragon.NUXI.org> <46F9A764.6000008@delphij.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: d@delphij.net, obrien@freebsd.org, freebsd-threads@freebsd.org Subject: Re: Renaming our threads libs X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 00:55:40 -0000 Daniel Eischen wrote: > On Tue, 25 Sep 2007, LI Xin wrote: > >> David O'Brien wrote: >>> We have little time before 7.0-RELEASE to get this right.. >>> >>> For consistency and expectations from users (especially of other OS's), >>> should we ask RE@ to rename libpthread to libkse (or whatever) and >>> rename >>> libthr to libpthread? Remember - what we release 7.0 will be burned >>> into >>> folks Makefile's and vernacular. >> >> Do you mean repocopy from src/lib/libpthread -> src/lib/libkse? Because >> libpthread.so.X is now installed as a symbolic link to actual default >> threading library I think it would be an overkill to rename libthr to >> libpthread, but to reduce confusion it might be better to rename >> lib/libpthread to lib/libkse. > > I think it's fine just the way it is. Everyone currently knows > libpthread and libthr by name. libpthread is currently installed > as libkse. I don't think you need to repo copy the src tree > to match, unless there is too much heartburn over having the > src directory named differently from the library. I think > libthr should remain named as it currently is. > > The links are a convenient way to swap between either of > the two (or future) libraries as default and still leave a > visible sign as to which library is the default. So I > really think those should stay as they are. for clarity I'd revert libpthread to libkse but leave libthr as it is.. > From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 04:53:15 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D212016A417; Wed, 26 Sep 2007 04:53:15 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id B05FE13C455; Wed, 26 Sep 2007 04:53:15 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id l8Q4r6Pi060872; Tue, 25 Sep 2007 21:53:06 -0700 (PDT) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.1/8.14.1/Submit) id l8Q4r6VR060871; Tue, 25 Sep 2007 21:53:06 -0700 (PDT) (envelope-from obrien) Date: Tue, 25 Sep 2007 21:53:06 -0700 From: "David O'Brien" To: Daniel Eischen Message-ID: <20070926045306.GB60798@dragon.NUXI.org> References: <20070926002038.GA56119@dragon.NUXI.org> <46F9A764.6000008@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.16 (2007-06-09) Cc: d@delphij.net, freebsd-threads@freebsd.org Subject: Re: Renaming our threads libs X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 04:53:15 -0000 On Tue, Sep 25, 2007 at 08:39:09PM -0400, Daniel Eischen wrote: > On Tue, 25 Sep 2007, LI Xin wrote: >> David O'Brien wrote: >>> We have little time before 7.0-RELEASE to get this right.. >>> >>> For consistency and expectations from users (especially of other OS's), >>> should we ask RE@ to rename libpthread to libkse (or whatever) and rename >>> libthr to libpthread? Remember - what we release 7.0 will be burned into >>> folks Makefile's and vernacular. >> >> Do you mean repocopy from src/lib/libpthread -> src/lib/libkse? Because >> libpthread.so.X is now installed as a symbolic link to actual default >> threading library I think it would be an overkill to rename libthr to >> libpthread, but to reduce confusion it might be better to rename >> lib/libpthread to lib/libkse. > > I think it's fine just the way it is. Everyone currently knows > libpthread and libthr by name. Everyone that has followed FreeBSD 7 from start to finish. There actually was confusion over this topic at the FreeBSD using company I work for. > I don't think you need to repo copy the src tree > to match, unless there is too much heartburn over having the > src directory named differently from the library. As I mentioned - I think there is unnecessary heartburn. -- -- David (obrien@FreeBSD.org) From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 04:57:33 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E97416A41A; Wed, 26 Sep 2007 04:57:33 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 1197513C45B; Wed, 26 Sep 2007 04:57:32 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id l8Q4vQYm060938; Tue, 25 Sep 2007 21:57:26 -0700 (PDT) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.1/8.14.1/Submit) id l8Q4vQx7060937; Tue, 25 Sep 2007 21:57:26 -0700 (PDT) (envelope-from obrien) Date: Tue, 25 Sep 2007 21:57:26 -0700 From: "David O'Brien" To: Daniel Eischen Message-ID: <20070926045726.GC60798@dragon.NUXI.org> References: <20070926002038.GA56119@dragon.NUXI.org> <46F9A764.6000008@delphij.net> <20070926004425.GF37370@elvis.mu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.16 (2007-06-09) Cc: d@delphij.net, freebsd-threads@freebsd.org Subject: Re: Renaming our threads libs X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 04:57:33 -0000 On Tue, Sep 25, 2007 at 08:53:07PM -0400, Daniel Eischen wrote: > On Tue, 25 Sep 2007, Alfred Perlstein wrote: >> The current situation only makes sense to those that have been >> watching the deal from day one, in "user land" confusion reigns >> and we're punishing those that choose our platform but letting >> it continue. > > And when someone has a threading bug, how are we suppose to > know which thread library it is in? Because if they linked with -lpthreads they were using libthr (after its repo-copied). If they say they linked with -lkse - we know that that is. There is also 'ldd' output. Only in folks that have been in the thick of our thread libs since the day 7.0 was born have the notion that libpthread is anything other than what is today called "libthr". > A simple 'ldd application' works if the thread libraries > stay named differently. And a simple 'ls -l /lib/libpthread*' > also works easily. > I don't see how installing either libthr or libkse as > libpthread is going to help. It's not clear which one is > "libpthread" that way. Its perfectly clear [after a repo-copy rename]. > The links make it clear, Only if we have access to the user's build machine - which we won't. If one wants to easily switch between thread libs for an already-compiled binary - we have /etc/libmap.conf for that. -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? Let's not play "Jeopardy-style quoting" From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 13:15:14 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B34216A41B; Wed, 26 Sep 2007 13:15:14 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 13DF413C4A5; Wed, 26 Sep 2007 13:15:13 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.1/8.14.1/NETPLEX) with ESMTP id l8QDF5Js012555; Wed, 26 Sep 2007 09:15:05 -0400 (EDT) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-3.0 (mail.netplex.net [204.213.176.10]); Wed, 26 Sep 2007 09:15:05 -0400 (EDT) Date: Wed, 26 Sep 2007 09:15:05 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "David O'Brien" In-Reply-To: <20070926045726.GC60798@dragon.NUXI.org> Message-ID: References: <20070926002038.GA56119@dragon.NUXI.org> <46F9A764.6000008@delphij.net> <20070926004425.GF37370@elvis.mu.org> <20070926045726.GC60798@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: d@delphij.net, freebsd-threads@freebsd.org Subject: Re: Renaming our threads libs X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 13:15:14 -0000 On Tue, 25 Sep 2007, David O'Brien wrote: > On Tue, Sep 25, 2007 at 08:53:07PM -0400, Daniel Eischen wrote: >> On Tue, 25 Sep 2007, Alfred Perlstein wrote: >>> The current situation only makes sense to those that have been >>> watching the deal from day one, in "user land" confusion reigns >>> and we're punishing those that choose our platform but letting >>> it continue. >> >> And when someone has a threading bug, how are we suppose to >> know which thread library it is in? > > Because if they linked with -lpthreads they were using libthr (after its > repo-copied). If they say they linked with -lkse - we know that that is. Asking them how they linked is after the fact and history tells us that we won't get a accurate answer to this question. > There is also 'ldd' output. Only in folks that have been in the thick of > our thread libs since the day 7.0 was born have the notion that > libpthread is anything other than what is today called "libthr". > > >> A simple 'ldd application' works if the thread libraries >> stay named differently. And a simple 'ls -l /lib/libpthread*' >> also works easily. > > >> I don't see how installing either libthr or libkse as >> libpthread is going to help. It's not clear which one is >> "libpthread" that way. > > Its perfectly clear [after a repo-copy rename]. It's not perfectly clear when DEFAULT_THREAD_LIB is anything other than libthr. I want -pthread to do the right thing regardless of which library is DEFAULT_THREAD_LIB, because -pthread is what we're telling everyone to use (well, it's what GCC is telling everyone to use). -- DE From owner-freebsd-threads@FreeBSD.ORG Wed Sep 26 17:10:02 2007 Return-Path: Delivered-To: freebsd-threads@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1854716A418 for ; Wed, 26 Sep 2007 17:10:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id EABF913C448 for ; Wed, 26 Sep 2007 17:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l8QHA1uQ009251 for ; Wed, 26 Sep 2007 17:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l8QHA1Mv009250; Wed, 26 Sep 2007 17:10:01 GMT (envelope-from gnats) Resent-Date: Wed, 26 Sep 2007 17:10:01 GMT Resent-Message-Id: <200709261710.l8QHA1Mv009250@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-threads@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, "Arno J. Klaassen" Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCE2916A41B for ; Wed, 26 Sep 2007 17:01:41 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id D59B913C46A for ; Wed, 26 Sep 2007 17:01:41 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.1/8.14.1) with ESMTP id l8QH1fc1020383 for ; Wed, 26 Sep 2007 17:01:41 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.1/8.14.1/Submit) id l8QH1fQc020382; Wed, 26 Sep 2007 17:01:41 GMT (envelope-from nobody) Message-Id: <200709261701.l8QH1fQc020382@www.freebsd.org> Date: Wed, 26 Sep 2007 17:01:41 GMT From: "Arno J. Klaassen" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: threads/116668: can no longer use jdk15 with libthr on -stable SMP X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 17:10:02 -0000 >Number: 116668 >Category: threads >Synopsis: can no longer use jdk15 with libthr on -stable SMP >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-threads >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Sep 26 17:10:01 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Arno J. Klaassen >Release: amd64 -stable >Organization: SCITO SA >Environment: FreeBSD install 6.2-STABLE FreeBSD 6.2-STABLE #2: Thu Sep 20 14:19:10 CEST 2007 toor@install:/usr/obj/files/bsd/src6/sys/S2881 amd64 >Description: jdk15 very easily hangs in 'umtx' or 'nanosleep' state when running with libthr on amd64-stable SMP. I do not see this behaviour on UP. Might not be related at all to libthr 'an sich', since I see the same with linux-sun-jdk14 >How-To-Repeat: put [/usr/local/jdk1.5.0/bin/javac] libpthread.so.2 libthr.so.2 in libmap.conf and then simply launce 'usr/local/jdk1.5.0/bin/javac ' after some repetitions javac will hang; you can kill it (but only with kill -9 ) >Fix: bon, don't use libthr with java on SMP systems ... >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-threads@FreeBSD.ORG Fri Sep 28 19:09:06 2007 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0EE916A418 for ; Fri, 28 Sep 2007 19:09:06 +0000 (UTC) (envelope-from sa2c@sa2c.net) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id 8192F13C48A for ; Fri, 28 Sep 2007 19:09:06 +0000 (UTC) (envelope-from sa2c@sa2c.net) Received: by wa-out-1112.google.com with SMTP id k17so3725958waf for ; Fri, 28 Sep 2007 12:09:06 -0700 (PDT) Received: by 10.114.154.1 with SMTP id b1mr1197398wae.1191004942378; Fri, 28 Sep 2007 11:42:22 -0700 (PDT) Received: from ?192.168.1.3? ( [220.102.212.119]) by mx.google.com with ESMTPS id j21sm6090260wah.2007.09.28.11.42.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 28 Sep 2007 11:42:21 -0700 (PDT) Message-ID: <46FD4B09.20006@sa2c.net> Date: Sat, 29 Sep 2007 03:42:17 +0900 From: NIIMI Satoshi MIME-Version: 1.0 To: freebsd-threads@freebsd.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: sched_yield() is very slow when other threads are busy on FreeBSD-current X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 19:09:06 -0000 Hi, I experienced sched_yield() is very slow when other threads are busy on FreeBSD-current. When I run the program: ------------------------------------------------ #include #include #include #define NUM_THREAD (10) volatile int run = 0; void *start(void *p) { while (!run) ; return p; } int main() { pthread_t th[NUM_THREAD]; int i; for (i = 0; i < NUM_THREAD; i++) { assert(pthread_create(&th[i], NULL, start, NULL) == 0); sched_yield(); } run = 1; for (i = 0; i < NUM_THREAD; i++) assert(pthread_join(th[i], NULL) == 0); return 0; } ------------------------------------------------ The output of /usr/bin/time: FreeBSD 6.2-RELEASE, libthr, HZ=100, GENERIC kernel: 0.55 real 0.55 user 0.00 sys FreeBSD 7-CURRENT, libthr, HZ=100, kernel include GENERIC nooptions INVARIANTS, INVARIANT_SUPPORT, WITNESS, WITNESS_SKIPSPIN: 164.16 real 162.80 user 0.00 sys I tried SCHED_ULE too, but does not help so much. Increasing HZ helps to perform better, but still very slower than FreeBSD-6. Thanks, -- NIIMI Satoshi