http://msdn.microsoft.com

If you come into the forums with a very stuck up attitude, you will find that you will not get much help.

Both Google and MSDN provide very simplified, broken down, and easy to understand and re-use demonstrations of multithreading; if you are unwilling to do the research required to learn from these very usefull resources, you probably should not be in the industry.

So, what you are saying is you want someone to take time out of their day to show you how to do something when you are apprently willing to put zero effort in yourself to find out how to do it?

News flash; programming is about problem solving. If you aren't willing to do some leg work yourself then you might as well give up now.

Yes, this forum is for helpping people however there is such a thing as 'give and take'; all that is asked is that you show what you've done to solve the problem on your own.

Coming in and saying 'show me how to do this' without any evidence of having used your own brain isn't what this is all about.

Anyway, despite your attitude I'll answer the 2nd half of your question as I'm here; threads are automatically scheulded to run on a free core or CPU when it is their turn. How this is done varies from OS to OS.

MSDN holds everything else you need to know about threads on windows.

Quote:Original post by BloodLust666
Actually that's not stuck up at all

True. Stuck up probably isn't the right word (for your post as it is now. I assume you've edited it). It is however, extremely lazy.

Is your time more valuable than ours? Should we spend 5 minutes of our time just to save you the same amount? Why, exactly?

Quote:i'm merely saying I would like someone to walk me through it as opposed to having someone refer me to a website that I could have gone to on my own.

We would all like a lot of things. Personally, I'd quite like someone to give me fifty thousand dollars, for example.

But if you could have looked it up on your own, why didn't you?

Quote:
It's a waste of a post and it only means you don't know how to do it either. If you do, SHOW me, don't refer me somewhere else and send me on a continued wild goose chase.

No, a waste of a post would be where you don't learn anything. The responses you've got above should have taught you much more than you'd have gotten if someone had just done your research for you. And how can it be a "continued wild goose chase"?
- "Continued" implies that you've already been searching for it, doesn't it? That doesn't seem to be the case. Nothing you've said in your posts so far indicate that you've tried to find the information yourself.
- "Wild goose chase" implies that it'd be a waste of time, that you'd never find what you needed. I don't see why that would be the case.


If you have searched for this information, and have been unable to find what you needed, then say so. And if that is the case, I'm sure a lots of people here would be happy to provide you with links to the necessary pages on MSDN (assuming you're working on Windows)

And finally, I suppose it can't hurt to help you out a bit.
You didn't say so, but I assume you're programming in C or C++, and I assume you're working on a Windows platform.
If so, you need to type the following into [Google]:
"windows create thread"

Click on the very first result.
Read that page.
You'll note the following:
1: It describes a function called CreateThread. Hmm, I wonder what that does.
2: Under "Example code", it contains a link named "Creating Threads". That might just have some of what you need.
3: It explains that under some circumstances, you should call a different function instead.

Now, once you've done the above, feel free to ask here if there's something you need clarified. There are plenty of people here who are happy to help beginners out. But it requires the beginner in question to do *some* of the work themselves.

Since you didn't say anything, I'm assuming this is for Windows and in C (or C++).

CreateThread and SetThreadAffinityMask.

CreateThread has an example on how to use it. SetThreadAffinityMask is fairly obvious.

Parallel processing is not such a simple topic that it can be well covered in a single post. Expecting people to recreate what has been covered in necessary detail in books is fairly unreasonable. If you cannot figure out how to use it on your own from the references and examples provided in the API, it's highly recommended you read a book on it. It's not something you're likely to get a good understanding of from an online tutorial (or forum post). Actually, even if you do figure out how to use it from the references, I'd still recommend reading a book. There are concerns to parallel code that are not immediately obvious just from looking at an API reference.

Wikipedia has a general introduction to the variety of issues that will come about in parallel coding. You should be able to get a reasonable idea of what to research from there based on your project's goals.