Please explain the following parallel code template

by

First, I’d like to say this is a bad place to ask question because you’ve obviously not done any research in to the matter yourself (especially as this template is pretty self explanatory).

I’ll explain it briefly for you however:

#include <omp.h>

Allows access to the openmp library so you can use all of its functions.

main () {

Please tell me you understand this line? It’s very bad practice to not return an int here however, you should really have an int main.

int var1, var2, var3;

Define 3 integers.
Where serial code is written, you can just read normal code here all executing on one thread/processor.

#pragma omp parallel private(var1, var2) shared(var3)

This line is perhaps the most important. It basically says the code in the next set of { } can be executed in parallel. private(var1, var2) means that each thread will get its own copy of these variables (I.e. thread 1’s var1 is not the same as thread 2’s var1) and shared(var3) means that var3 is the same on all threads (and if it changes on thread 1, it also changes on thread 2)

The code executes in parallel until that } is reached at which point the code returns to normal operating mode if you like on one thread.

You should really read some basic OMP tutorials which you can find anywhere on the internet with a very simple google.

I hope this gets you started though.

More Related Contents:

  1. HOW I CALCULATE TIME IN C PROGRAM
  2. sending blocks of 2D array in C using MPI
  3. Concurrency: Atomic and volatile in C++11 memory model
  4. Is malloc thread-safe?
  5. How do I start threads in plain C?
  6. When the main thread exits, do other threads also exit?
  7. Signal handling with multiple threads in Linux
  8. Difference between section and task openmp
  9. How expensive is the lock statement?
  10. No performance gain after using openMP on a program optimize for sequential running
  11. Can I get Unix’s pthread.h to compile in Windows?
  12. Scatter Matrix Blocks of Different Sizes using MPI
  13. fork and existing threads?
  14. Pthread Run a thread right after it’s creation
  15. Do threads have a distinct heap?
  16. Why is Parallel.ForEach much faster then AsParallel().ForAll() even though MSDN suggests otherwise?
  17. Using C/Pthreads: do shared variables need to be volatile?
  18. Reductions in parallel in logarithmic time
  19. Is it possible to access/update the child thread’s resource from parent thread?
  20. Linux/POSIX equivalent for Win32’s CreateEvent, SetEvent, WaitForSingleObject
  21. Should thread-safe class have a memory barrier at the end of its constructor?
  22. Multiple threads and CPU cache
  23. MPI_Type_create_subarray and MPI_Gather
  24. Break parallel.foreach?
  25. What is the difference between fork and thread?
  26. Can multithreading be implemented on a single processor system?
  27. How to properly parallelise job heavily relying on I/O
  28. How to get the number of CPUs in Linux using C?
  29. Why is the != operator not allowed with OpenMP?
  30. Wait for QueueUserWorkItem to Complete

Leave a Comment