From owner-freebsd-threads@FreeBSD.ORG Mon Dec 13 11:02:23 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B73CE16A4CE for ; Mon, 13 Dec 2004 11:02:23 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BCAD43D1F for ; Mon, 13 Dec 2004 11:02:23 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBDB2NOW075256 for ; Mon, 13 Dec 2004 11:02:23 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBDB2Mq8075250 for freebsd-threads@freebsd.org; Mon, 13 Dec 2004 11:02:22 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 13 Dec 2004 11:02:22 GMT Message-Id: <200412131102.iBDB2Mq8075250@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-threads@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Dec 2004 11:02:24 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/04/22] threads/65883threads libkse's sigwait does not work after fork 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/07/18] kern/20016 threads pthreads: Cannot set scheduling timer/Can o [2000/08/26] kern/20861 threads libc_r does not honor socket timeouts o [2001/01/20] threads/24472threads libc_r does not honor SO_SNDTIMEO/SO_RCVT o [2001/01/25] threads/24632threads libc_r delicate deviation from libc in ha o [2001/01/25] kern/24641 threads pthread_rwlock_rdlock can deadlock o [2001/11/26] bin/32295 threads pthread dont dequeue signals o [2002/02/01] threads/34536threads accept() blocks other threads o [2002/05/25] kern/38549 threads the procces compiled whith pthread stoppe o [2002/06/27] threads/39922threads [PATCH?] Threaded applications executed w o [2002/08/04] kern/41331 threads Pthread library open sets O_NONBLOCK flag o [2003/03/02] threads/48856threads Setting SIGCHLD to SIG_IGN still leaves z o [2003/03/10] threads/49087threads Signals lost in programs linked with libc o [2003/05/08] threads/51949threads thread in accept cannot be cancelled s [2004/03/15] kern/64313 threads FreeBSD (OpenBSD) pthread implicit set/un o [2004/08/26] threads/70975threads unexpected and unreliable behaviour when o [2004/09/14] threads/71725threads Mysql Crashes frequently giving Sock Erro o [2004/10/05] threads/72353threads Assertion fails in /usr/src/lib/libpthrea o [2004/10/07] threads/72429threads threads blocked in stdio (fgets, etc) are o [2004/10/21] threads/72953threads fork() unblocks blocked signals w/o PTHRE o [2004/11/25] threads/74370threads Cannot get lwp 0 registers in gdb o [2004/12/08] threads/74856threads dig/host broken w/ libthr 21 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/05/26] kern/18824 threads gethostbyname is not thread safe o [2000/06/13] kern/19247 threads uthread_sigaction.c does not do anything o [2000/10/21] kern/22190 threads A threaded read(2) from a socketpair(2) f o [2001/09/09] threads/30464threads pthread mutex attributes -- pshared o [2002/05/02] threads/37676threads libc_r: msgsnd(), msgrcv(), pread(), pwri s [2002/07/16] threads/40671threads pthread_cancel doesn't remove thread from o [2004/07/13] threads/69020threads pthreads library leaks _gc_mutex o [2004/09/21] threads/71966threads Mlnet Core Dumped : Fatal error '_pq_inse o [2004/11/21] threads/74180threads KSE problem. Applications those riched ma 9 problems total. From owner-freebsd-threads@FreeBSD.ORG Wed Dec 15 18:54:38 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9955316A4CE for ; Wed, 15 Dec 2004 18:54:38 +0000 (GMT) Received: from silver.he.iki.fi (helenius.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BA1643D39 for ; Wed, 15 Dec 2004 18:54:37 +0000 (GMT) (envelope-from pete@he.iki.fi) Received: from [193.64.42.134] (h86.vuokselantie10.fi [193.64.42.134]) by silver.he.iki.fi (8.13.1/8.11.4) with ESMTP id iBFIsZDo038951 for ; Wed, 15 Dec 2004 20:54:35 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <41C0886C.7040704@he.iki.fi> Date: Wed, 15 Dec 2004 20:54:36 +0200 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-threads@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: malloc / free and profiling X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2004 18:54:38 -0000 Is it a known problem that libpthread with -pg (gprof stuff) does not work properly but gets random hangs in malloc / free routines? (5.3-RELEASE) Same code with gcov or no profiling at all works fine. Pete From owner-freebsd-threads@FreeBSD.ORG Wed Dec 15 18:59:25 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3B0816A4CE for ; Wed, 15 Dec 2004 18:59:25 +0000 (GMT) Received: from silver.he.iki.fi (helenius.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FFA443D64 for ; Wed, 15 Dec 2004 18:59:25 +0000 (GMT) (envelope-from pete@he.iki.fi) Received: from [193.64.42.134] (h86.vuokselantie10.fi [193.64.42.134]) by silver.he.iki.fi (8.13.1/8.11.4) with ESMTP id iBFIxOVL038989 for ; Wed, 15 Dec 2004 20:59:24 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <41C0898E.3090005@he.iki.fi> Date: Wed, 15 Dec 2004 20:59:26 +0200 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-threads@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: worker thread performance question X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2004 18:59:25 -0000 With libpthread is it usually optimal to have as many worker threads (CPU bound stuff) as kern.threads.virtual_cpu or have, say double the number so that there is always a thread in the run queue when another hits a mutex or sleep? Pete From owner-freebsd-threads@FreeBSD.ORG Wed Dec 15 19:39:23 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7846E16A4CE for ; Wed, 15 Dec 2004 19:39:23 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FD9443D55 for ; Wed, 15 Dec 2004 19:39:23 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 35E8D7A403; Wed, 15 Dec 2004 11:39:23 -0800 (PST) Message-ID: <41C092EA.7060100@elischer.org> Date: Wed, 15 Dec 2004 11:39:22 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Petri Helenius References: <41C0898E.3090005@he.iki.fi> In-Reply-To: <41C0898E.3090005@he.iki.fi> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-threads@freebsd.org Subject: Re: worker thread performance question X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2004 19:39:23 -0000 Petri Helenius wrote: > > With libpthread is it usually optimal to have as many worker threads > (CPU bound stuff) as kern.threads.virtual_cpu or have, say double the > number so that there is always a thread in the run queue when another > hits a mutex or sleep? Are they always runnable? theoretically you can schedule as many as you want. any number > NCPU should keep teh system busy, but I'm not sure I fully understand the question. > > > Pete > > _______________________________________________ > 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" From owner-freebsd-threads@FreeBSD.ORG Wed Dec 15 19:47:31 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EEED16A4CE for ; Wed, 15 Dec 2004 19:47:31 +0000 (GMT) Received: from silver.he.iki.fi (helenius.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76A8043D1F for ; Wed, 15 Dec 2004 19:47:30 +0000 (GMT) (envelope-from pete@he.iki.fi) Received: from [193.64.42.134] (h86.vuokselantie10.fi [193.64.42.134]) by silver.he.iki.fi (8.13.1/8.11.4) with ESMTP id iBFJlLDv039310; Wed, 15 Dec 2004 21:47:21 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <41C094CB.9010009@he.iki.fi> Date: Wed, 15 Dec 2004 21:47:23 +0200 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julian Elischer References: <41C0898E.3090005@he.iki.fi> <41C092EA.7060100@elischer.org> In-Reply-To: <41C092EA.7060100@elischer.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-threads@freebsd.org Subject: Re: worker thread performance question X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2004 19:47:31 -0000 Julian Elischer wrote: > > > Petri Helenius wrote: > >> >> With libpthread is it usually optimal to have as many worker threads >> (CPU bound stuff) as kern.threads.virtual_cpu or have, say double the >> number so that there is always a thread in the run queue when another >> hits a mutex or sleep? > > > Are they always runnable? Almost, except when they run into shared structures which obviously are minimized by design. > theoretically you can schedule as many as you want. > any number > NCPU should keep teh system busy, but > I'm not sure I fully understand the question. The question was aimed towards if larger runqueue takes more CPU to maintain than a shorter one does and if threads are involuntarily switched. Pete > >> >> >> Pete >> >> _______________________________________________ >> 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" > > > From owner-freebsd-threads@FreeBSD.ORG Wed Dec 15 20:19:40 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36DD716A4CE for ; Wed, 15 Dec 2004 20:19:40 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0299843D45 for ; Wed, 15 Dec 2004 20:19:40 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id BFB487A44A; Wed, 15 Dec 2004 12:19:39 -0800 (PST) Message-ID: <41C09C5B.7060706@elischer.org> Date: Wed, 15 Dec 2004 12:19:39 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Petri Helenius References: <41C0898E.3090005@he.iki.fi> <41C092EA.7060100@elischer.org> <41C094CB.9010009@he.iki.fi> In-Reply-To: <41C094CB.9010009@he.iki.fi> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-threads@freebsd.org Subject: Re: worker thread performance question X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Dec 2004 20:19:40 -0000 Petri Helenius wrote: > Julian Elischer wrote: > >> >> >> Petri Helenius wrote: >> >>> >>> With libpthread is it usually optimal to have as many worker threads >>> (CPU bound stuff) as kern.threads.virtual_cpu or have, say double >>> the number so that there is always a thread in the run queue when >>> another hits a mutex or sleep? >> >> >> >> Are they always runnable? > > > Almost, except when they run into shared structures which obviously > are minimized by design. > >> theoretically you can schedule as many as you want. >> any number > NCPU should keep teh system busy, but >> I'm not sure I fully understand the question. > > > The question was aimed towards if larger runqueue takes more CPU to > maintain than a shorter one does and if threads are involuntarily > switched. yes and yes. > > > Pete > >> >>> >>> >>> Pete >>> >>> _______________________________________________ >>> 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" >> >> >> >>