tbb

Abstracting Thread Local Storage

[Disclaimer: I'm sketching possibilities here. There is no commitment from the TBB group to implement any of this.]

Threading packages often have some notion of a thread id or thread local storage. The two are equivalent in the sense if given one, you can easily build the other. For example, thread local storage can be implemented as a one-to-one map from thread ids to pieces of storage. And vice versa, the address of a variable in thread-local storage can be used as a thread id.

Integrating Python and Threading Building Blocks, Part 3

Continuing my effort to create an application that has a Python GUI and a back-end C++ computation engine that is threaded using Threading Building Blocks, I followed the instructions in the "Boost.Python Build and Test HOWTO" about how to relocate my Boost.Python "quickstart" application, so I can modify it as I'd like.

Integrating Python and Threading Building Blocks, Part 2

In my last post, I installed the Boost C++ libraries onto my Windows machine, and verified that the installation was successful. Now it's time to get Boost.Python operational, so I can get closer to my objective of creating a Threading Building Blocks application that is run using a Python user interface.

Integrating Python and Threading Building Blocks, Part 1

Several months ago, I began working on integrating Threading Building Blocks with scripting languages, such as Perl and Python. In the past week I've reexamined this problem from a new point of view: focusing on a single scripting language, rather than trying to come up with a single solution that will work for multiple languages.

Interesting Multicore Crisis Graph and Analysis

I came across a very interesting blog post as I was perusing the Net last night. Bob Warfield, who writes the SmoothSpan Blog, which focuses primarily on SaaS and Web 2.0, posted a very interesting blog titled "Apple, MacWorld, User Experience, and the Multicore Crisis".

Installing Threading Building Blocks on Debian Etch

In my last post, "Threading Building Blocks Debian Linux Packages", I successfully added Debian TBB package maintainer Roberto Sanchez's personal Debian Etch package site to my /etc/apt/sources.list on my Debian 4.0 (Etch) system. One more step was necessary in order for me to be able to actually access Roberto's packages:

apt-get update

Threading Building Blocks Build Makefiles

In my last post, I outlined the Threading Building Blocks build structure. In this post, I'll look at the makefiles for a particular platform. Once you understand how these makefiles are organized, you'll have a roadmap for porting TBB to new platforms.

The Threading Building Blocks Build Structure

My work on building Threading Building Blocks on UWIN led me to a fairly detailed study of the TBB build structure. Having studied this, and not finding documentation of it elsewhere, I thought I'd share what I've learned thus far, before I return to my UWIN work.

The TBB build directory

Linked Lists - Incompatible with Parallel Programming?

I've been asked several times why TBB does not have a concurrent list class; i.e., a list that supports concurrent access. The answer is that we'd add one if:

We could figure out semantics that are useful for parallel programming and

We could implement it reasonably efficiently on current hardware.

I usually try to avoid linked lists even for sequential programming if I'm programming for performance. My reasons are:

Building Threading Building Blocks on UWIN, Part 3

In Part 2 of this series on building Threading Building Blocks on the UWIN platform, I had reached the point where much had been resolved; but my UWIN build was returning "unknown" as the value of the TBB runtime variable. The next step was to trace how runtime gets set and figure out what I need to do to get it set correctly.

Intel® Developer Zone

tbb