From owner-freebsd-arch@FreeBSD.ORG Wed Dec 3 22:52:33 2008 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4963106564A; Wed, 3 Dec 2008 22:52:33 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3AAEC8FC16; Wed, 3 Dec 2008 22:52:32 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id mB3MqPKL023152; Wed, 3 Dec 2008 17:52:26 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Lawrence Stewart Date: Wed, 3 Dec 2008 15:02:41 -0500 User-Agent: KMail/1.9.7 References: <492412E8.3060700@freebsd.org> <200812021707.41545.jhb@freebsd.org> <4935E4B5.6090204@freebsd.org> In-Reply-To: <4935E4B5.6090204@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200812031502.42218.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Wed, 03 Dec 2008 17:52:26 -0500 (EST) X-Virus-Scanned: ClamAV 0.93.1/8718/Wed Dec 3 08:29:03 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-arch@freebsd.org Subject: Re: kthread_exit(9) unexpectedness X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2008 22:52:33 -0000 On Tuesday 02 December 2008 08:45:25 pm Lawrence Stewart wrote: > > might even be better to add a dedicated condvar to 'struct thread' in 8.x > > that is used for the wakeup and do the wakeup on that rather than the thread > > pointer to be honest. > > > > What are the pros/cons of using mtx_sleep/wakeup vs cv_wait/cv_broadcast? Forces you to use explicit wait channels as opposed to some of the problems we have now with 3-4 places sleeping on proc pointers for example. -- John Baldwin