From owner-freebsd-threads@FreeBSD.ORG Tue Jun 17 06:22:16 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 C27CB37B401 for ; Tue, 17 Jun 2003 06:22:16 -0700 (PDT) Received: from rwcrmhc11.attbi.com (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3574143F75 for ; Tue, 17 Jun 2003 06:22:16 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([12.233.125.100]) by attbi.com (rwcrmhc11) with ESMTP id <2003061706094101300am5i2e>; Tue, 17 Jun 2003 06:09:41 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id XAA25090; Mon, 16 Jun 2003 23:09:40 -0700 (PDT) Date: Mon, 16 Jun 2003 23:09:39 -0700 (PDT) From: Julian Elischer To: Terry Lambert In-Reply-To: <3EEEADF5.6DC76F9F@mindspring.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org cc: zander@mail.minion.de cc: Gareth Hughes cc: 'Daniel Eischen' cc: Andy Ritger 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 13:22:17 -0000 Terry, don't go overboard.. I think we can work with this.. I have some ideas.. We may be able to cut it down to 2 instructions in general and one for the N:N case using linker relaxation. It depends on how much we can hack teh linker to do similar stuff to what linux does, but notice tht on a fully dynamically linked object it looks like the Optimised 1 instruction version can't be used anyhow. (well it needs a bit more thinking but it may not be as bad as it seemed at first.) In the M:N case we can probably have the Userland thread scheduler set a pointer to the TLD blocks into the KSE mailox each time a new thread is scheduled.. %gs would be left the same but what it points to could be changed cheaply. On Mon, 16 Jun 2003, Terry Lambert wrote: > Gareth Hughes wrote: > > On Mon, 16 Jun 2003, Daniel Eischen wrote: > > > Right. It just seems wrong to me to be able to insert __thread > > > after every global variable in a library and instantly make > > > it thread-safe. > > > > Why, exactly? Surely, from a programming point of view, this is > > exactly what you want -- a transparent way to access your thread > > local data. > > No, what you want first and foremost is your code to compile and > run on all platforms, without limiting your market by relying on > defacto language extensions that have not been explicitly and > intentionally standardized by a recognized standards body. > > -- Terry > _______________________________________________ > 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" >