Project

General

Profile

Bug #1441

Lies at startup about "The comm. thread both sends and receives messages"

Added by Jim Phillips 7 months ago. Updated 4 days ago.

Status:
New
Priority:
Urgent
Assignee:
Category:
Machine Layers
Target version:
Start date:
02/21/2017
Due date:
% Done:

0%


Description

There is logic for setting and reporting Cmi_smp_mode_setting at startup, but this only reflects the behavior of the mpi-smp and gni-smp layers.

jim@sunnyvale$grep -r Cmi_smp_mode_setting .
./arch/util/machine-common-core.c:static enum MACHINE_SMP_MODE Cmi_smp_mode_setting = COMM_THREAD_SEND_RECV;
./arch/util/machine-common-core.c:      if (Cmi_smp_mode_setting == COMM_THREAD_SEND_RECV) {
./arch/util/machine-common-core.c:      } else if (Cmi_smp_mode_setting == COMM_THREAD_ONLY_RECV) {
./arch/util/machine-common-core.c:      } else if (Cmi_smp_mode_setting == COMM_WORK_THREADS_SEND_RECV) {
./arch/util/machine-common-core.c:      } else if (Cmi_smp_mode_setting == COMM_THREAD_NOT_EXIST) {
./arch/util/machine-common-core.c:    if(Cmi_smp_mode_setting == COMM_THREAD_ONLY_RECV
./arch/util/machine-common-core.c:       || Cmi_smp_mode_setting == COMM_THREAD_NOT_EXIST)
./arch/mpi/machine.c:    if (Cmi_smp_mode_setting == COMM_THREAD_SEND_RECV) {
./arch/mpi/machine.c:  if (Cmi_smp_mode_setting == COMM_THREAD_ONLY_RECV) {
./arch/mpi/machine.c:    if(Cmi_smp_mode_setting == COMM_THREAD_SEND_RECV){
./arch/mpi/machine.c:    }else if(Cmi_smp_mode_setting == COMM_THREAD_ONLY_RECV) {
./arch/mpi/machine.c:      Cmi_smp_mode_setting = COMM_THREAD_ONLY_RECV;
./arch/mpi/machine.c:    if (Cmi_smp_mode_setting == COMM_THREAD_SEND_RECV)
./arch/mpi/machine.c:    if (Cmi_smp_mode_setting == COMM_THREAD_ONLY_RECV && _thread_provided != MPI_THREAD_MULTIPLE) {
./arch/mpi/machine.c:        Cmi_smp_mode_setting = COMM_THREAD_SEND_RECV; 
./arch/gni/machine.c:    Cmi_smp_mode_setting = COMM_WORK_THREADS_SEND_RECV;

History

#1 Updated by Jim Phillips 7 months ago

More specifically, verbs and net-ibverbs only use the comm thread for receives.

#2 Updated by Sam White 7 months ago

  • Assignee set to Nitin Bhat
  • Target version set to 6.8.0

#3 Updated by Phil Miller 7 months ago

  • Assignee changed from Nitin Bhat to Jaemin Choi

#4 Updated by Phil Miller 6 months ago

  • Priority changed from Normal to Urgent

Setting priority higher because these are easy to fix things that act as paper-cuts to users

#5 Updated by Jaemin Choi 6 months ago

  • Status changed from New to Implemented

#6 Updated by Sam White 6 months ago

  • Subject changed from lies at startup about "The comm. thread both sends and receives messages" to Lies at startup about "The comm. thread both sends and receives messages"
  • Status changed from Implemented to Merged

#7 Updated by Nitin Bhat 25 days ago

  • Target version changed from 6.8.0 to 6.8.1
  • Status changed from Merged to New

A pamilrts-smp build, which doesn't use a worker thread, also displays this message "The comm. thread both sends and receives messages". Additionally, it'll be good to do a rundown of smp builds for all machine layers and test if the comm thread mode is displayed correctly.

#8 Updated by Phil Miller 11 days ago

Nitin, could you follow up with checks on the other layers and note whether/what needs to be done here?

#9 Updated by Nitin Bhat 4 days ago

Sure. I'll do that.

Also available in: Atom PDF