From owner-freebsd-threads@FreeBSD.ORG Wed Dec 21 18:07:12 2011 Return-Path: Delivered-To: threads@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07129106566C; Wed, 21 Dec 2011 18:07:12 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe03.c2i.net [212.247.154.66]) by mx1.freebsd.org (Postfix) with ESMTP id 2338B8FC13; Wed, 21 Dec 2011 18:07:10 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe03.swip.net (CommuniGate Pro SMTP 5.4.2) with ESMTPA id 53409308; Wed, 21 Dec 2011 18:57:06 +0100 From: Hans Petter Selasky To: freebsd-arch@freebsd.org Date: Wed, 21 Dec 2011 18:54:40 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <4EF084A8.32369.B604AD16@s_sourceforge.nedprod.com> In-Reply-To: X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201112211854.40798.hselasky@c2i.net> Cc: threads@freebsd.org, Warner Losh , arch@freebsd.org Subject: Re: [Patch] C1X threading support 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, 21 Dec 2011 18:07:12 -0000 On Wednesday 21 December 2011 18:33:16 Warner Losh wrote: > On Dec 20, 2011, at 5:50 AM, Niall Douglas wrote: > > The job was NOT done half-arsed. If you had any experience of sitting > > on these committees you would know how much dedication and effort is > > put into standards, especially JTC1 SC22 subcommittees. Every single > > API in there has been studied and pored over at length across > > multiple years. > > > > Everything is the way it is for a good reason. If it doesn't make > > sense to you that's most likely because you're not half as > > experienced or clever as you think you are. If you really want to > > know why something is the way it is, all discussion regarding all > > points is documented in full. > > Incredible claims require incredible proof. The APIs speak for themselves: > they are half-assed (and the wrong half in some cases). To assert that > they are somehow clever and we're stupid requires that one walk through > the cleverness. The participants in this thread likely have a combined > century of implementation experience with threads. > > Perhaps you can point us to the archives where all this discussion is > available? > Hi, Absolute timeouts is no good idea! We should stick with kernel-ticks when possible :-) --HPS