From owner-freebsd-threads@FreeBSD.ORG Mon Jun 16 15:20:08 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 4FF4337B407 for ; Mon, 16 Jun 2003 15:20:08 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0A4A43FBD for ; Mon, 16 Jun 2003 15:20:07 -0700 (PDT) (envelope-from eischen@pcnet.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h5GMK0Xh012314; Mon, 16 Jun 2003 18:20:00 -0400 (EDT) Date: Mon, 16 Jun 2003 18:20:00 -0400 (EDT) From: Daniel Eischen To: Julian Elischer In-Reply-To: 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: 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: Mon, 16 Jun 2003 22:20:08 -0000 On Mon, 16 Jun 2003, Julian Elischer wrote: > > On Mon, 16 Jun 2003, Gareth Hughes wrote: > > > On Mon, 16 Jun 2003, Andy Ritger wrote: > > > > > > So from an OpenGL point of view, here are several alternatives that > > > I see for atleast the near term: > > > > > > - make NVIDIA's OpenGL implementation not thread-safe (just > > > use global data rather that thread-local data) > > > > > > - accept the performance hit of using pthread_getspecific() > > > on FreeBSD. From talking to other OpenGL engineers, > > > conservative estimates of the performance impact on > > > applications like viewperf range from 10% - 15%. I'd like > > > to quantify that, but certainly there will be a performance > > > penalty. > > > > And these are *very* conservative estimates -- you're essentially adding a > > function call into a path that is, on average, less than ten instructions > > per OpenGL API call, where the number of API calls per frame is upward of 3 I see this as a problem with the OpenGL API. You're trying to make something thread-safe that isn't by its nature. I would rather see OpenGL-MT with new interfaces that are by nature thread-safe. -- Dan Eischen