From owner-freebsd-threads@FreeBSD.ORG Mon Jun 16 18:18:41 2003 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 BAD8D37B401 for ; Mon, 16 Jun 2003 18:18:41 -0700 (PDT) Received: from mx2.mail.ru (mx2.mail.ru [194.67.23.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07B3B43FCB for ; Mon, 16 Jun 2003 18:18:41 -0700 (PDT) (envelope-from kabaev@mail.ru) Received: from [151.203.235.42] (port=55759 helo=kan.dnsalias.net) by mx2.mail.ru with esmtp id 19S57O-000JCo-00; Tue, 17 Jun 2003 05:18:39 +0400 Received: from kan.dnsalias.net (ak03@localhost [127.0.0.1]) by kan.dnsalias.net (8.12.9/8.12.9) with ESMTP id h5H1IaTI090294; Mon, 16 Jun 2003 21:18:36 -0400 (EDT) (envelope-from kan@kan.dnsalias.net) Received: (from kan@localhost) by kan.dnsalias.net (8.12.9/8.12.9/Submit) id h5H1IZb3090293; Mon, 16 Jun 2003 21:18:35 -0400 (EDT) Date: Mon, 16 Jun 2003 21:18:35 -0400 From: Alexander Kabaev To: Gareth Hughes Message-Id: <20030616211835.10d0fba4.kabaev@mail.ru> In-Reply-To: <2D32959E172B8F4D9B02F68266BE421401A6D7E6@mail-sc-3.nvidia.com> References: <2D32959E172B8F4D9B02F68266BE421401A6D7E6@mail-sc-3.nvidia.com> X-Mailer: Sylpheed version 0.9.0claws2 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam: Not detected cc: threads@freebsd.org cc: zander@mail.minion.de cc: 'Julian Elischer' cc: Andy Ritger cc: 'Daniel Eischen' Subject: Re: NVIDIA and TLS 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: Tue, 17 Jun 2003 01:18:42 -0000 On Mon, 16 Jun 2003 18:11:30 -0700 Gareth Hughes wrote: > > If FreeBSD support ELF TLS and __thread variables in ANY form, our > driver will use this support. If the best you can do is a function > call per access, so be it. It doesn't sound like there are any other > options, given the fact that you ship with three different thread > libraries. Three different libraries can attempt to coordinate and reserve exactly the same TLS segment size.