From owner-freebsd-current@FreeBSD.ORG Tue Feb 24 17:06:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA94416A4CE for ; Tue, 24 Feb 2004 17:06:26 -0800 (PST) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EF0043D46 for ; Tue, 24 Feb 2004 17:06:26 -0800 (PST) (envelope-from julian@elischer.org) Received: from interjet.elischer.org ([24.7.73.28]) by comcast.net (sccrmhc13) with ESMTP id <2004022501062501600d7v9ae>; Wed, 25 Feb 2004 01:06:25 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id RAA82348 for ; Tue, 24 Feb 2004 17:06:23 -0800 (PST) Date: Tue, 24 Feb 2004 17:06:22 -0800 (PST) From: Julian Elischer To: FreeBSD current users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: TLS, Thread Local Storage.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2004 01:06:26 -0000 Now that the real threading libraries are in more common usage we need to tackle TLS. The TLS spec is NOT part of posix, but people are starting to write software that depends on it (e.g. nvidia) and that is the real definition of our requirements. The definative doc is at: http://people.redhat.com/drepper/tls.pdf We can handle the kernel side pretty much already (We've had our eye on this for a while) but it's the tools, linker etc that are going to be the problems.. The library parts are "understood". This is basically a call to find out "who is interested?" Some people have already indicated some interest but don't let that stop them from piping up again now.. (people often are interested in something but time constraints etc. change and...)