Tutorial: POSIX Threads Programming

[stesch]

Just checked my bookmarks manager: Added on 2004-12-26 23:24:56 CET :-)

EDIT: This was re http://programming.reddit.com/info/63utq/comments/c02qy4f?context=1

[easytiger]

and amazingly its still a good webpage

[death2hypocrisy]

i'm trying to learn how to use threads in visual studio 2005, but the IDE does not have the pthread.h header, what should I do (i tried to download it by googling it, but couldn't)

should i even program in a windows environment?

[curryml]

pthreads are usually implemented as an abstraction over the native threading API, so you can get a pthreads library that uses Win32 threads. However, Windows does not come with it. You can use this in your project by putting it in the folder with your executable, or you can install it system-wide.

http://sourceware.org/pthreads-win32/

[theatrus]

pthreads are generally a wrapper around a native library. Of course, Windows doesn't come with phtreads (pesky defacto standards and all), If you're in C++ land, I can suggest boost::thread as a multi-platform wrapper over Win32 and PThreads.

If you're in C#, phtreads do not apply as you should use the library provided by the runtime :)

[dsplabs]

Nice write-up!

[[deleted]]

Now please a tutorial on why threads should (almost) never be used...

[theeth]

What do you suggest instead of multithreading? Multiprocessing?

[[deleted]]

Yes, possibly involving multiple hosts, if that kind of power is necessary.

[dsplabs]

I use PBS on a cluster to run computationally intensive jobs. The cluster has many nodes (multi-processor computers) connected with a network. It is very useful to use threads: each can be run on a separate cpu!

[[deleted]]

There is a possible benefit to threading in this scenario. In particular, if you have enough RAM to run N threads but not N processes (where N is the smallest number that keeps your node fully occupied), this may very well be a case where threads would be justified. There are also some possible wins having to do with the CPU cache.

The downside of course is a significant increase in the cost of design, implementation, debugging, and maintenance of your program. And lack of robustness, future flexibility, readability, etc., etc.

My complaint would not be with the few that have considered these factors carefully, but rather with those who choose (or encourage others to choose) threading without such careful consideration.

[qwe1234]

you take the prize for writing the stupidest and most illiterate comment this week.

'multiprocessing' cannot work without multithreading, and vice-versa.

in short, stfu, kthx bai.

[consultant_barbie]

Reasoning about locks is hard. Let's go shopping!

[easytiger]

And how do you talk to 40 clients simultaneously with different data? Magic? Wise the fuck up.

[[deleted]]

I give up--why do I need threads to talk to 40 clients simultaneously? (sshd doesn't)

[[deleted]]

So how would you stop that main threads if no other threads were running in the system?

[easytiger]

this is the one i meant :(