OpenMP parallel loop without using $OMP DO

Question

I was looking at a program using the FORTRAN version of OPENMP. There I encountered a rather strange construct. For making a "do" loop parallel the following construct was used

count = 0
!$OMP PARALLEL     
    do
      if (count > N ) exit
        !$OMP CRITICAL
           count = count + 1
        !$OMP END CRITICAL

        call WORK ! do some work here
     end do
 !$OMP END PARALLEL

I am not really sure, whether the above code is really making the do loop parallel. I know that the standard method of doing this is to use the following work sharing construct.

!$OMP PARALLEL     
!$OMP DO
   do count = 1,N
        call WORK ! do some work here
     end do
!$OMP ENDDO
!$OMP END PARALLEL

I have tested both possibilities, by implementing the standard work-sharing construct, and observed some speedup, when using it. I can imagine that the $OMP CRITICAL construct might be acting as a bottle neck and causing some slowing down. I think that using the non standard method for work sharing, might be beneficial if threads were executing at different speed. However, I am not really sure how accurate my thoughts are.

Thank you in advance

Alex

Hristo Iliev · Accepted Answer · 2014-06-06 14:05:26Z

2

Your thoughts are correct and what the original code does is the equivalent of:

!$OMP PARALLEL DO SCHEDULE(DYNAMIC) 
do count = 0,N
  call WORK ! do some work here
end do
!$OMP END PARALLEL DO

Basically it implements dynamic loop scheduling in a very awkward and inefficient way. If call WORK takes always the same amount of time, i.e. there are no conditions that result in work imbalance, then the SCHEDULE(DYNAMIC) clause can be replaced by SCHEDULE(STATIC) for improved performance.

answered Jun 6, 2014 at 14:05

Hristo Iliev

74.8k12 gold badges147 silver badges197 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Alexander Cska Over a year ago

Thank you for your reply. Quite happy having my humble assumptions confirmed. I was suspecting this would turn out being a soft soap.

Vladimir F Героям слава · Accepted Answer · 2014-06-06 12:04:34Z

1

If the !$omp do is not used, then every thread does the same as the other ones. The omp do directive is meant to divide the space of indexes of the loop between the threads. The threads don't do the same work, but run different iterations of the numbered loop. In your case there are no indexes here, so nothing to be divided, all threads will run the same code.

For just updating the count omp atomic could be used, but if WORK takes long enough to compute it may be negligible. I am worried that there is also problem reading count in the condition in the original code.

count = 0
!$OMP PARALLEL     
    do
      !$OMP ATOMIC READ
      count2 = count
      if (count2 > N ) exit
        !$OMP ATOMIC UPDATE
           count = count + 1

        call WORK ! do some work here
     end do
 !$OMP END PARALLEL

The intention here is to call WORK N times and do individual calls in parallel. There may be more elegant ways to achieve this.

edited Jun 6, 2014 at 12:04

answered Jun 6, 2014 at 9:29

Vladimir F Героям слава

60.7k4 gold badges82 silver badges131 bronze badges

1 Comment

Alexander Cska Over a year ago

Hi, thank you for your reply. It turns out that my initial assumptions were indeed correct.

Collectives™ on Stack Overflow

OpenMP parallel loop without using $OMP DO

2 Answers 2

1 Comment

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related