From owner-freebsd-threads@FreeBSD.ORG Mon Jan 12 11:07:00 2009 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 E805A10656C0 for ; Mon, 12 Jan 2009 11:07:00 +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 D35038FC18 for ; Mon, 12 Jan 2009 11:07:00 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0CB708U092155 for ; Mon, 12 Jan 2009 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0CB70MY092151 for freebsd-threads@FreeBSD.org; Mon, 12 Jan 2009 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 12 Jan 2009 11:07:00 GMT Message-Id: <200901121107.n0CB70MY092151@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 freebsd-threads@FreeBSD.org 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, 12 Jan 2009 11:07:02 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o threa/129956 threads Threaded process stuck in "vmopar" state, other in "uf o threa/128922 threads threads hang with xorg running o threa/128180 threads pthread_cond_broadcast(3) lost wakeup o threa/127225 threads bug in lib/libthr/thread/thr_init.c o threa/122923 threads 'nice' does not prevent background process from steali o threa/121336 threads lang/neko threading ok on UP, broken on SMP (FreeBSD 7 o threa/118715 threads kse problem o threa/116668 threads can no longer use jdk15 with libthr on -stable SMP o threa/116181 threads /dev/io-related io access permissions are not propagat o threa/115211 threads pthread_atfork misbehaves in initial thread o threa/110636 threads [request] gdb(1): using gdb with multi thread applicat o threa/110306 threads apache 2.0 segmentation violation when calling gethost o threa/103975 threads Implicit loading/unloading of libpthread.so may crash o threa/101323 threads [patch] fork(2) in threaded programs broken. s threa/100815 threads FBSD 5.5 broke nanosleep in libc_r s threa/94467 threads send(), sendto() and sendmsg() are not correct in libc s threa/84483 threads problems with devel/nspr and -lc_r on 4.x o threa/83914 threads [libc] popen() doesn't work in static threaded program o threa/80992 threads abort() sometimes not caught by gdb depending on threa o threa/80435 threads panic on high loads o threa/79887 threads [patch] freopen() isn't thread-safe o threa/79683 threads svctcp_create() fails if multiple threads call at the s threa/76694 threads fork cause hang in dup()/close() function in child (-l s threa/76690 threads fork hang in child for -lc_r o threa/75374 threads pthread_kill() ignores SA_SIGINFO flag o threa/75273 threads FBSD 5.3 libpthread (KSE) bug o threa/72953 threads fork() unblocks blocked signals w/o PTHREAD_SCOPE_SYST o threa/70975 threads [sysvipc] unexpected and unreliable behaviour when usi s threa/69020 threads pthreads library leaks _gc_mutex s threa/49087 threads Signals lost in programs linked with libc_r s threa/48856 threads Setting SIGCHLD to SIG_IGN still leaves zombies under s threa/40671 threads pthread_cancel doesn't remove thread from condition qu s threa/39922 threads [threads] [patch] Threaded applications executed with s threa/37676 threads libc_r: msgsnd(), msgrcv(), pread(), pwrite() need wra s threa/34536 threads accept() blocks other threads s threa/32295 threads [libc_r] [patch] pthread(3) dont dequeue signals s threa/30464 threads pthread mutex attributes -- pshared s threa/24632 threads libc_r delicate deviation from libc in handling SIGCHL s threa/24472 threads libc_r does not honor SO_SNDTIMEO/SO_RCVTIMEO socket o 39 problems total. From owner-freebsd-threads@FreeBSD.ORG Mon Jan 12 20:49:59 2009 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 0D94B1065678 for ; Mon, 12 Jan 2009 20:49:59 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from gw.sandvine.com (gw.sandvine.com [199.243.201.138]) by mx1.freebsd.org (Postfix) with ESMTP id BE9BD8FC1F for ; Mon, 12 Jan 2009 20:49:58 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from labgw2.phaedrus.sandvine.com ([192.168.3.11]) by gw.sandvine.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 12 Jan 2009 15:37:57 -0500 Received: by labgw2.phaedrus.sandvine.com (Postfix, from userid 12627) id 8F35513613; Mon, 12 Jan 2009 15:37:57 -0500 (EST) Date: Mon, 12 Jan 2009 15:37:57 -0500 From: Ed Maste To: Alfred Perlstein Message-ID: <20090112203757.GA10620@sandvine.com> References: <200811041440.mA4Ee31J084489@freefall.freebsd.org> <20081104154113.GP60438@elvis.mu.org> <20081104180349.GA9527@sandvine.com> <20081104190221.GT60438@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081104190221.GT60438@elvis.mu.org> User-Agent: Mutt/1.4.2.1i X-OriginalArrivalTime: 12 Jan 2009 20:37:57.0788 (UTC) FILETIME=[A7357DC0:01C974F5] Cc: freebsd-threads@FreeBSD.org Subject: Re: threads/128180: pthread_cond_broadcast(3) lost wakeup 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, 12 Jan 2009 20:49:59 -0000 On Tue, Nov 04, 2008 at 11:02:21AM -0800, Alfred Perlstein wrote: > * Ed Maste [081104 10:03] wrote: > > On Tue, Nov 04, 2008 at 07:41:13AM -0800, Alfred Perlstein wrote: > > > > > This bug may have been fixed in 6-stable and 6.4. > > > > > > http://svn.freebsd.org/viewvc/base?view=revision&revision=184172 > > > > > > Can you try upgrading? > > > > I tried with the changes from r184172, but I'm still able to reproduce > > the problem using the test app in the PR. With your change it does > > seem to run for on average about 10 times as long before it hangs though. > > Hmm... I'll look into it. Did you have a chance to look into it at all? I didn't really test it very thoroughly, so my my comment about running 10 times as long may not be right -- my main concern is that the test app still does demonstrate the problem with r184172 applied. -Ed From owner-freebsd-threads@FreeBSD.ORG Wed Jan 14 17:06:08 2009 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 6377010656E9; Wed, 14 Jan 2009 17:06:08 +0000 (UTC) (envelope-from kib@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 356B58FC24; Wed, 14 Jan 2009 17:06:08 +0000 (UTC) (envelope-from kib@FreeBSD.org) Received: from freefall.freebsd.org (kib@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0EH689n050825; Wed, 14 Jan 2009 17:06:08 GMT (envelope-from kib@freefall.freebsd.org) Received: (from kib@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0EH68UL050821; Wed, 14 Jan 2009 17:06:08 GMT (envelope-from kib) Date: Wed, 14 Jan 2009 17:06:08 GMT Message-Id: <200901141706.n0EH68UL050821@freefall.freebsd.org> To: pluknet@gmail.com, kib@FreeBSD.org, freebsd-threads@FreeBSD.org, kib@FreeBSD.org From: kib@FreeBSD.org Cc: Subject: Re: threads/129956: Threaded process stuck in "vmopar" state, other in "ufs" later. 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, 14 Jan 2009 17:06:11 -0000 Synopsis: Threaded process stuck in "vmopar" state, other in "ufs" later. State-Changed-From-To: open->analyzed State-Changed-By: kib State-Changed-When: Wed Jan 14 17:05:34 UTC 2009 State-Changed-Why: I have a working patch for the problem. Responsible-Changed-From-To: freebsd-threads->kib Responsible-Changed-By: kib Responsible-Changed-When: Wed Jan 14 17:05:34 UTC 2009 Responsible-Changed-Why: I have a working patch for the problem. http://www.freebsd.org/cgi/query-pr.cgi?pr=129956 From owner-freebsd-threads@FreeBSD.ORG Thu Jan 15 03:16:46 2009 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 7F7F01065674 for ; Thu, 15 Jan 2009 03:16:46 +0000 (UTC) (envelope-from pramod@juniper.net) Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by mx1.freebsd.org (Postfix) with ESMTP id 468D18FC14 for ; Thu, 15 Jan 2009 03:16:46 +0000 (UTC) (envelope-from pramod@juniper.net) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKSW6qnlBip5u2XOC2wM3pRnt5qvkewlrs@postini.com; Wed, 14 Jan 2009 19:16:46 PST Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.336.0; Wed, 14 Jan 2009 18:57:50 -0800 Received: from emailcorp3.jnpr.net ([66.129.254.13]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 14 Jan 2009 18:57:50 -0800 Received: from 172.24.24.209 ([172.24.24.209]) by emailcorp3.jnpr.net ([66.129.254.13]) with Microsoft Exchange Server HTTP-DAV ; Thu, 15 Jan 2009 02:57:50 +0000 User-Agent: Microsoft-Entourage/12.0.0.071130 Date: Wed, 14 Jan 2009 18:57:57 -0800 From: Pramod Srinivasan To: Message-ID: Thread-Topic: Priority scheduling in 6.x Thread-Index: Acl2vRFsQ5ix+ococ0+YiP/8ZMqG9Q== MIME-Version: 1.0 X-OriginalArrivalTime: 15 Jan 2009 02:57:50.0153 (UTC) FILETIME=[0D57E390:01C976BD] Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Priority scheduling in 6.x 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: Thu, 15 Jan 2009 03:16:46 -0000 Hi, I have 3 threads low, medium and high , and the scheduling policy is set to SCHED_FIFO. The priority of the threads are at 28,29,30 respectively. Looks like on FreeBSD 6.x, the priority of the threads are not honored while scheduling the threads, but the same test on FreeBSD 7.x seems to work fine. Are there known issues with the priority scheduling in FreeBSD 6.x or am I doing something wrong? (I am using libthr) Any input highly appreciated. Thanks, Pramod From owner-freebsd-threads@FreeBSD.ORG Thu Jan 15 03:43:17 2009 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 CE03A106567E for ; Thu, 15 Jan 2009 03:43: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 8EE878FC0C for ; Thu, 15 Jan 2009 03:43: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.3/8.14.3/NETPLEX) with ESMTP id n0F3Pfww018556; Wed, 14 Jan 2009 22:25:41 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Wed, 14 Jan 2009 22:25:41 -0500 (EST) Date: Wed, 14 Jan 2009 22:25:41 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Pramod Srinivasan In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-threads@freebsd.org Subject: Re: Priority scheduling in 6.x 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: Thu, 15 Jan 2009 03:43:18 -0000 On Wed, 14 Jan 2009, Pramod Srinivasan wrote: > Hi, > > I have 3 threads low, medium and high , and the scheduling policy is set to > SCHED_FIFO. The priority of the threads are at 28,29,30 respectively. Looks > like on FreeBSD 6.x, the priority of the threads are not honored while > scheduling the threads, but the same test on FreeBSD 7.x seems to work fine. > Are there known issues with the priority scheduling in FreeBSD 6.x or am I > doing something wrong? (I am using libthr) Are you using libpthread or libthr on 6.3? If you are using libthr, then you need to be running with superuser privileges for SCHED_FIFO to work. I'm not sure if this works correctly at all in 6.3. If you are using libpthread, then it will work if the threads are PTHREAD_SCOPE_PROCESS, but will not work if they are PTHREAD_SCOPE_SYSTEM. You do not need superuser privileges for SCHED_FIFO with libpthread and process scope threads. I don't believe the kernel has ever worked properly for libpthread (kse) SCHED_FIFO system scope threads. -- DE From owner-freebsd-threads@FreeBSD.ORG Thu Jan 15 22:21:42 2009 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 118AA1065672 for ; Thu, 15 Jan 2009 22:21:42 +0000 (UTC) (envelope-from pramod@juniper.net) Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by mx1.freebsd.org (Postfix) with ESMTP id C3C1D8FC12 for ; Thu, 15 Jan 2009 22:21:41 +0000 (UTC) (envelope-from pramod@juniper.net) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKSW+29UnScoy4vtktNWxaPKAR2uXP5pUs@postini.com; Thu, 15 Jan 2009 14:21:41 PST Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.336.0; Thu, 15 Jan 2009 14:19:02 -0800 Received: from emailcorp3.jnpr.net ([66.129.254.13]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 15 Jan 2009 14:19:02 -0800 Received: from 172.23.1.52 ([172.23.1.52]) by emailcorp3.jnpr.net ([66.129.254.13]) with Microsoft Exchange Server HTTP-DAV ; Thu, 15 Jan 2009 22:19:02 +0000 User-Agent: Microsoft-Entourage/12.0.0.071130 Date: Thu, 15 Jan 2009 14:19:09 -0800 From: Pramod Srinivasan To: Daniel Eischen Message-ID: Thread-Topic: Priority scheduling in 6.x Thread-Index: Acl3X0ks/0ytv3fge0a4i9mYY2iZoA== In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Jan 2009 22:19:02.0493 (UTC) FILETIME=[454B48D0:01C9775F] Cc: freebsd-threads@freebsd.org Subject: Re: Priority scheduling in 6.x 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: Thu, 15 Jan 2009 22:21:42 -0000 Hi Daniel Thanks for your response. On 1/14/09 7:25 PM, "Daniel Eischen" wrote: > On Wed, 14 Jan 2009, Pramod Srinivasan wrote: > >> Hi, >> >> I have 3 threads low, medium and high , and the scheduling policy is set to >> SCHED_FIFO. The priority of the threads are at 28,29,30 respectively. Looks >> like on FreeBSD 6.x, the priority of the threads are not honored while >> scheduling the threads, but the same test on FreeBSD 7.x seems to work fine. >> Are there known issues with the priority scheduling in FreeBSD 6.x or am I >> doing something wrong? (I am using libthr) > > Are you using libpthread or libthr on 6.3? I am using libthr on 6.1, but had similar issues on 6.2 as well. > > If you are using libthr, then you need to be running with > superuser privileges for SCHED_FIFO to work. I'm not sure > if this works correctly at all in 6.3. I am running the program with super user privileges on 6.1, tried this on 6.2 as well. Priority scheduling using libthr does not work, unless I am missing something very basic?. The same program works fine on 7.1, any ideas? > > If you are using libpthread, then it will work if the > threads are PTHREAD_SCOPE_PROCESS, but will not work > if they are PTHREAD_SCOPE_SYSTEM. You do not need > superuser privileges for SCHED_FIFO with libpthread > and process scope threads. I don't believe the kernel > has ever worked properly for libpthread (kse) SCHED_FIFO > system scope threads. I tried libpthread with PTHREAD_SCOPE_PROCESS, it was better, I see that the priority is honored. Thanks for the pointer. Thanks, Pramod From owner-freebsd-threads@FreeBSD.ORG Thu Jan 15 22:38:45 2009 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 AD2511065694 for ; Thu, 15 Jan 2009 22:38:45 +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 6BCF38FC21 for ; Thu, 15 Jan 2009 22:38:45 +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.3/8.14.3/NETPLEX) with ESMTP id n0FMchI7028104; Thu, 15 Jan 2009 17:38:43 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Thu, 15 Jan 2009 17:38:44 -0500 (EST) Date: Thu, 15 Jan 2009 17:38:43 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Pramod Srinivasan In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-threads@freebsd.org Subject: Re: Priority scheduling in 6.x 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: Thu, 15 Jan 2009 22:38:47 -0000 On Thu, 15 Jan 2009, Pramod Srinivasan wrote: > Hi Daniel > > Thanks for your response. > > On 1/14/09 7:25 PM, "Daniel Eischen" wrote: > >> On Wed, 14 Jan 2009, Pramod Srinivasan wrote: >> >>> Hi, >>> >>> I have 3 threads low, medium and high , and the scheduling policy is set to >>> SCHED_FIFO. The priority of the threads are at 28,29,30 respectively. Looks >>> like on FreeBSD 6.x, the priority of the threads are not honored while >>> scheduling the threads, but the same test on FreeBSD 7.x seems to work fine. >>> Are there known issues with the priority scheduling in FreeBSD 6.x or am I >>> doing something wrong? (I am using libthr) >> >> Are you using libpthread or libthr on 6.3? > > I am using libthr on 6.1, but had similar issues on 6.2 as well. > >> >> If you are using libthr, then you need to be running with >> superuser privileges for SCHED_FIFO to work. I'm not sure >> if this works correctly at all in 6.3. > > I am running the program with super user privileges on 6.1, tried this on > 6.2 as well. Priority scheduling using libthr does not work, unless I am > missing something very basic?. The same program works fine on 7.1, any > ideas? I'm not sure what kernel scheduler you are using (ULE or BSD), but you can try switching it. Other than that, it probably just won't ever work correctly on 6.x. -- DE From owner-freebsd-threads@FreeBSD.ORG Thu Jan 15 23:22:50 2009 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 D753B106564A; Thu, 15 Jan 2009 23:22:50 +0000 (UTC) (envelope-from pramod@juniper.net) Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by mx1.freebsd.org (Postfix) with ESMTP id 7AE268FC1E; Thu, 15 Jan 2009 23:22:50 +0000 (UTC) (envelope-from pramod@juniper.net) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKSW/FSbvdZxp/djniu4hqTDH/RDOQqY/V@postini.com; Thu, 15 Jan 2009 15:22:50 PST Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.336.0; Thu, 15 Jan 2009 15:20:28 -0800 Received: from emailcorp3.jnpr.net ([66.129.254.13]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 15 Jan 2009 15:20:28 -0800 Received: from 172.23.1.52 ([172.23.1.52]) by emailcorp3.jnpr.net ([66.129.254.13]) with Microsoft Exchange Server HTTP-DAV ; Thu, 15 Jan 2009 23:20:28 +0000 User-Agent: Microsoft-Entourage/12.0.0.071130 Date: Thu, 15 Jan 2009 15:20:35 -0800 From: Pramod Srinivasan To: Daniel Eischen Message-ID: Thread-Topic: Priority scheduling in 6.x Thread-Index: Acl3Z94zu2MiLsw4A0Ow2GGhzJE0mw== In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Jan 2009 23:20:28.0564 (UTC) FILETIME=[DA5D1540:01C97767] Cc: freebsd-threads@freebsd.org Subject: Re: Priority scheduling in 6.x 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: Thu, 15 Jan 2009 23:22:51 -0000 On 1/15/09 2:38 PM, "Daniel Eischen" wrote: > I'm not sure what kernel scheduler you are using (ULE or BSD), > but you can try switching it. Other than that, it probably > just won't ever work correctly on 6.x. I tried both ULE and BSD, does not work. Do you think that an effort to back port any fixes that may have gone into 7.x too difficult? From owner-freebsd-threads@FreeBSD.ORG Thu Jan 15 23:27:13 2009 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 7933B106566B for ; Thu, 15 Jan 2009 23:27: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 388838FC17 for ; Thu, 15 Jan 2009 23:27: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.3/8.14.3/NETPLEX) with ESMTP id n0FNRBIE017825; Thu, 15 Jan 2009 18:27:12 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Thu, 15 Jan 2009 18:27:12 -0500 (EST) Date: Thu, 15 Jan 2009 18:27:11 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Pramod Srinivasan In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-threads@freebsd.org Subject: Re: Priority scheduling in 6.x 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: Thu, 15 Jan 2009 23:27:14 -0000 On Thu, 15 Jan 2009, Pramod Srinivasan wrote: > On 1/15/09 2:38 PM, "Daniel Eischen" wrote: > >> I'm not sure what kernel scheduler you are using (ULE or BSD), >> but you can try switching it. Other than that, it probably >> just won't ever work correctly on 6.x. > > I tried both ULE and BSD, does not work. Do you think that an effort to back > port any fixes that may have gone into 7.x too difficult? I don't know - 7.x/8.x have changed significantly from 6.x. 6.x is basically dead, all new work goes into -current and 7.x. -- DE