Return-Path: <tiff-bounces@lists.maptools.org>
Received: from inas024.isp.belgacom.be (localhost [127.0.0.1])
        by inav006.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-AV-3.00) with ESMTP id k8N15iba011483
        for <joris.at.lebbeke@skynet.be>; Sat, 23 Sep 2006 03:05:44 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from inmx010.isp.belgacom.be (inmx010.isp.belgacom.be [195.238.4.73])
        by inas024.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-AS-2.03) with ESMTP id k8N15dAu017888
        for <joris.at.lebbeke@skynet.be>; Sat, 23 Sep 2006 03:05:40 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx010.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-2.32) with ESMTP id k8N15SsG025098
        for <joris.at.lebbeke@skynet.be>; Sat, 23 Sep 2006 03:05:29 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (duke.maptools.org [127.0.0.1])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id k8N0sAEZ010001;
	Fri, 22 Sep 2006 20:54:57 -0400
Received: from mail03.yourhostingaccount.com (mail03.yourhostingaccount.com
	[65.254.254.67])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id k8N0s8VU009998
	for <tiff@lists.maptools.org>; Fri, 22 Sep 2006 20:54:08 -0400
Received: from scan10.yourhostingaccount.com ([10.1.1.240]
	helo=scan10.yourhostingaccount.com)
	by mail03.yourhostingaccount.com with esmtp (Exim)
	id 1GQvmQ-0006Hk-6H
	for tiff@lists.maptools.org; Fri, 22 Sep 2006 20:54:06 -0400
Received: from authsmtp02.yourhostingaccount.com ([10.1.1.156] ident=exim)
	by scan10.yourhostingaccount.com with spamscanlookuphost (Exim)
	id 1GQvmQ-0005Q3-7b
	for tiff@lists.maptools.org; Fri, 22 Sep 2006 20:54:06 -0400
Received: from authsmtp02.yourhostingaccount.com ([10.1.1.156]
	helo=authsmtp02.yourhostingaccount.com)
	by scan10.yourhostingaccount.com with esmtp (Exim)
	id 1GQvmP-0005Q0-T1
	for tiff@lists.maptools.org; Fri, 22 Sep 2006 20:54:05 -0400
Received: from cust3861.vic01.dataco.com.au ([202.164.193.21] helo=[10.0.0.1])
	by authsmtp02.yourhostingaccount.com with esmtpsa (TLSv1:RC4-MD5:128)
	(Exim) id 1GQvmP-0004sJ-4y
	for tiff@lists.maptools.org; Fri, 22 Sep 2006 20:54:05 -0400
Message-ID: <4514851A.5000505@argyllcms.com>
Date: Sat, 23 Sep 2006 10:51:38 +1000
From: Graeme Gill <graeme2@argyllcms.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: tiff@lists.maptools.org
Subject: Re: [Tiff] libjpeg
References: <20060922164741.2AE9765D99@mail.business.allstream.net>
	<Pine.SOC.4.60.0609221158050.1941@blade.simplesystems.org>
In-Reply-To: <Pine.SOC.4.60.0609221158050.1941@blade.simplesystems.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-EN-UserInfo: 4278ddcaa0afbc5edf619268be555fc4:fcefc52a98eff5eb12ac042c4438d4fd
X-EN-AuthUser: graeme@argyllcms.com
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
Precedence: list
Reply-To: graeme@argyllcms.com
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=subscribe>
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
X-UIDL: 000000000023ceae.00001add
X-MSP-STORE: Sat, 23 Sep 2006 03:05:48 +0200
Status:   

Bob Friesenhahn wrote:
> The next (latest?) big thing in CPU architectures is to provide hardware 
> support for thread contexts so that if a thread would be delayed by a 
> slow memory access, a different thread can be scheduled to run 
> instantaneously.  

Bob, in the popular arena, it's practically been and gone ! :-)
SMT (Simultaneous MultiThreading, or Hyper-Threading Technology,
as Intel like to call it) is a Pentium 4 feature, and
Pentium 4's are now being phased out in favour of the Core
architecture (which is more of a reversion to the
P6/PentiumPro/Pentium3 scheme of things). Currently no Core
processor supports SMT (although I guess it may appear again
at some stage, and/or other manufacturers may incorporate it),
instead all the emphasis in the x86 world now seems to be on
multi core processors, where each core only executes one thread.

Just to comment on thread safety, another tool available to
solve some of these sorts of problems is thread local storage.
MSWindows certainly has it, and so apparently does POSIX threads.

Graeme Gill.
_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
