/[MITgcm]/MITgcm/eesupp/src/check_threads.F

Diff of /MITgcm/eesupp/src/check_threads.F

Parent Directory | Revision Log | View Revision Graph Revision Graph | View Patch Patch

-revision 1.1 by cnh,
Wed Apr 22 19:15:30 1998 UTC
+revision 1.13 by edhill,
Sat Mar 27 03:51:50 2004 UTC
 Line 1
- C $Id$
+ C $Header$
+ C $Name$
  #include "CPP_EEOPTIONS.h"
- CStartOfInterface
+ CBOP
+ C     !ROUTINE: CHECK_THREADS
+ C     !INTERFACE:
        SUBROUTINE CHECK_THREADS( myThid )
- C     /==========================================================\
+       IMPLICIT NONE
- C     | SUBROUTINE CHECK_THREADS                                 |
- C     | o Check that all the threads we need did indeed start.   |
+ C     !DESCRIPTION:
- C     |==========================================================|
+ C     *==========================================================
- C     | This routine is called during the initialisation phase   |
+ C     | SUBROUTINE CHECK\_THREADS
- C     | to check whether all the threads have started.           |
+ C     | o Check that all the threads we need did indeed start.
- C     | It is invoked by every thread and if any thread finds an |
+ C     *==========================================================
- C     | error it should set its error flag.                      |
+ C     | This routine is called during the initialisation phase
- C     | Notes:                                                   |
+ C     | to check whether all the threads have started.
- C     |  Different mechanisms may be required on different       |
+ C     | It is invoked by every thread and if any thread finds an
- C     | platforms to actually perform the check. For example as  |
+ C     | error it should set its error flag.
- C     | coded here each thread checks for a semaphore set by the |
+ C     | Notes:
- C     | other threads to see if they are running.                |
+ C     |  Different mechanisms may be required on different
- C     | It is also possible for a system to schedule threads     |
+ C     | platforms to actually perform the check. For example as
- C     | sequentially, unless some system call is made to yield   |
+ C     | coded here each thread checks for a semaphore set by the
- C     | the process. This routine would detect this situation too|
+ C     | other threads to see if they are running.
- C     | and allow a programmer to modify this routine and the    |
+ C     | It is also possible for a system to schedule threads
- C     | barrier code to allow threads to be scheduled more       |
+ C     | sequentially, unless some system call is made to yield
- C     | appropriately.                                           |
+ C     | the process. This routine would detect this situation too
- C     \==========================================================/
+ C     | and allow a programmer to modify this routine and the
+ C     | barrier code to allow threads to be scheduled more
+ C     | appropriately.
+ C     *==========================================================
- C     === Global data ===
+ C     !USES:
+ C     == Global variables ==
  #include "SIZE.h"
  #include "EEPARAMS.h"
  #include "EESUPPORT.h"
- C     === Routine areguments ===
- C     myThid - My thread number
-       INTEGER myThid
- CEndOfInterface
+ C     !INPUT PARAMETERS:
+ C     == Routine arguments ==
+ C     myThid :: My thread number
+       INTEGER myThid
- C     === Local variables ===
+ C     !LOCAL VARIABLES:
- C     I - Loop counter
+ C     == Local variables ==
- C     numberThreadRunning - Count of number of threads this thread
+ C     I :: Loop counter
- C                           thinks are running.
+ C     numberThreadRunning :: Count of number of threads this thread
- C     nChecks - Number of times checked for all threads. After so
+ C                            thinks are running.
- C               many checks give up and report an error.
+ C     nChecks   :: Number of times checked for all threads. After so
+ C                  many checks give up and report an error.
+ C     msgBuffer :: Temp. for preparing text messages.
        INTEGER I
        INTEGER numberThreadsRunning
        INTEGER nChecks
        CHARACTER*(MAX_LEN_MBUF) msgBuffer
+ CEOP
  C
        threadIsRunning(myThid) = .TRUE.
        nChecks                 = 0
-Line 59 
 C
+Line 71 
 C
        IF ( nChecks .GT. 10 ) THEN
         thError(myThid) = .TRUE.
         eeBootError     = .TRUE.
-        WRITE(msgBuffer,'(A,I,A,I,A)')
+        WRITE(msgBuffer,'(A,I5,A,I5,A)')
       &  'S/R INI_CHECK_THREADS: Only ',numberThreadsRunning,
       &  ' thread(s), ',nThreads,' are needed for this configuration!'
          CALL PRINT_ERROR( msgBuffer , myThid)
  C--     Not enough threads are running so halt the program.
- C       I didn't want this here but it is the only place I have found that
+ C       I did not want this here but it is the only place I have found that
  C       KAP deadlocks if it there are fewer threads than iterations in a BLOCKED(1)
  C       loop. The deadlock appears to be in the routine mppjoin which never
  C       returns. I tried putting the STOP in main or breaking out of the loop in main
-Line 75 
 C       but this causes KAP to insert a
+Line 87 
 C       but this causes KAP to insert a
         GOTO 11
        ENDIF
        IF ( numberThreadsRunning .NE. nThreads ) THEN
+ #ifdef HAVE_SYSTEM
         CALL SYSTEM('sleep 1')
+ #endif
         GOTO 10
        ENDIF
 CONTINUE
- C
- C
        RETURN
        END
- C $Id$

 Legend:



Removed from v.1.1
 


changed lines


 
Added in v.1.13
 Legend:



Removed from v.1.1
 


changed lines


 
Added in v.1.13
-Removed from v.1.1
+Added in v.1.13

	ViewVC Help
Powered by ViewVC 1.1.22